Access
Which enabled policies govern each agent and tool pair, and which effects their rules can produce. This is scope, not permission: the effect for a real request depends on its parameters at request time.
◆ declared agent lists the tool (not enforced)
A ALLOW ALLOW R REQUIRE_APPROVAL REQUIRE_APPROVAL D DENY DENY
possible
Empty cell: no policy in scope, engine default applies
| Agent |
stripe.refund
|
stripe.get_charge
|
github.create_issue
|
|---|---|---|---|
|
finance-agent
active
finance
|
finance-agent, stripe.refund:
◆ declared
FINANCE-004
A ALLOWR REQUIRE_APPROVALD DENY
|
finance-agent, stripe.get_charge:
◆ declared
No policy in scope
|
finance-agent, github.create_issue:
not declared
GITHUB-002
A ALLOWR REQUIRE_APPROVALD DENY
|
|
engineering-agent
active
engineering
|
engineering-agent, stripe.refund:
not declared
FINANCE-004
A ALLOWR REQUIRE_APPROVALD DENY
|
engineering-agent, stripe.get_charge:
not declared
No policy in scope
|
engineering-agent, github.create_issue:
◆ declared
GITHUB-002
A ALLOWR REQUIRE_APPROVALD DENY
|
A policy in scope does not mean the action is authorized. Scope is decided by the policy’s selectors; the effect is decided per request by the rules, and a suspended agent is refused at authentication before any policy is consulted.