Access — ARC Control

◆ declared agent lists the tool (not enforced) A ALLOW R REQUIRE_APPROVAL D DENY possible Empty cell: no policy in scope, engine default applies

Access matrix: agents by tools, showing policies in scope
Agent	stripe.refund irreversible critical	stripe.get_charge read low	github.create_issue write medium
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

engineering-agent → github.create_issue

Declared by the agent. Not a grant.

GITHUB-002 Repository writes

tools:github.*

1 no-default-branch

when branch is one of ["main", "master", "release"]

agents may not write to a protected branch

DENY
2 issues-and-prs

when tool.name is one of ["github.create_issue", "github.create_pull_request"]

opening issues and pull requests is reviewable by design

ALLOW
Fallback
if no rule matched: unclassified repository write
REQUIRE_APPROVAL

Across policies the strictest effect wins. Which rung fires depends on the request’s parameters.

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.