Use AI. Keep control. Empower your people.

Explore Athena

Secure Runtime

Approved is not the same as executed

A person approves one action. An agent submits another. The difference can be a changed recipient, a larger amount or an unintended retry.

12 May 2026 · 3 min read

Updated 28 October 2026

← All articles

Look at the actual action

A reviewer approves a payment to one supplier. Before submission, the destination changes. The workflow still has an approval, but the submitted action no longer matches it.

The same problem appears in code and infrastructure. Approval to prepare a patch does not authorise a production deployment. A button labelled Approve cannot be expected to explain all this on its own.

Define what the approval covers

Specify the actor, operation, resource, relevant arguments, time window and permitted use. The connected enforcement point must check the submitted request against that scope before allowing it.

A supported workflow can bind the approved proposal to the request presented for execution. Changing a protected field should require a new approval. A repeated submission needs an explicit replay or retry rule, rather than an assumption that the earlier approval remains spendable.

Test the awkward cases

Start with a permitted action that succeeds. Then make changes that should be refused. The test needs the real connection, not just an approval screen.

  • Change a recipient, target environment or protected argument.
  • Use an expired approval or the wrong identity.
  • Replay an approval intended for one use.
  • Interrupt a required policy or approval check.
  • Check how an uncertain receiving-system outcome is reported.

Keep the proposal and outcome distinct

An approval says what someone permitted. A submission says what the connected runtime requested. The receiving system reports an outcome. Keep those stages identifiable in the record.

Athena Secure Runtime applies checks at supported connected action points. Its records help reviewers examine the approval scope, the submitted action and the reported result. Activity outside those points needs its own controls and evidence.

Ask the question that matters

Can the team show that this submitted action matched this approval, under these conditions? Nearby timestamps can help an investigation, but they do not answer that question by themselves.

Test the mismatch, not just the happy path. Two green entries saying approved and executed can look excellent in a dashboard while describing two different things. Matching colours are not the relationship you need.

Sources and further reading

Originally published 12 May 2026. Rewritten on 28 October 2026.

OWASP: excessive agency

Athena Secure Runtime

Keep exploring