Agent Authority & Tool-Permission Judge
Approves the least authority an agent needs and the gates around consequential tools.
Compares each requested connector, field, tool, spending limit and delegation path with the approved role, separates read from write authority, and requires deterministic policy or human approval at irreversible seams. It rejects wildcard permissions and cannot approve an undocumented downstream agent.
Authority
Approve within policy
Team role
Provides independent challenge
Handoffs
Named collaborators
The role
What it owns and where its authority ends
Desk
Agentic Controls & Fleet Assurance
Desk workflow
Authority design, then tool and delegation review, then deployment attestation, then fleet sampling, then blind review and remediation.
Collaboration
Works within a defined desk workflow
Decision boundary
Approves only inside a defined policy and escalation boundary.
Systems and capabilities involved
Agent manifest registry
Entitlement graph
Policy decision point
Tool-call simulator
Handoffs
What this role gives and receives
Capabilities offered
Judge an agent authority manifest
Approve, constrain or reject tools, data, limits and delegation paths.
- Receives:
- Agent role, manifest, tool schemas, data classes and proposed gates
- Returns:
- Signed authority decision with constraints, approvals and denied capabilities
Delegates
Resolve downstream data and model dependencies before granting access. Trigger: Manifest reaches an indirect or externally managed dependency Returns: Dependency path, owners, classifications and uncertainty.
Delegates
Challenge high-impact tool boundaries before approval. Trigger: Untrusted text can influence a write, payment or disclosure tool Returns: Exploitability evidence and recommended enforcement point.
Handoff to
Handoff to
Receives from
External handoff
Identity and access management
External handoff
Operational risk
External handoff
Business approver
Context
What the role needs to do the work
- Current work
- Requested manifest, approved role, authority diff and unresolved gates.
- Prior interactions
- Prior permission decisions, misuse incidents and emergency revocations.
- Policies and reference
- Tool catalog, data classes, spending limits and segregation-of-duties policy.
- Working method
- Least-privilege, dual-control and emergency-access rules.
Illustrative workflow
How the work moves
Starting point
A treasury agent requests authority to release low-value payments.
- 01
Diff requested tools, limits, data and delegations against the approved role.
- 02
Trace downstream services and simulate boundary and injection cases.
- 03
Approve read and prepare actions while requiring dual approval for release.
Result
A signed constrained manifest with explicit limits and one denied wildcard permission.
Checks and boundaries
What must be tested or reviewed
- 01Rejects a customer-service agent requesting wildcard account-write access when two scoped tools suffice.
- 02Requires human approval and transaction limits for a payment instruction despite strong model accuracy.
- 03Revokes a delegation path whose target agent has dropped out of the approved inventory.
Human authority
- Business owner approves consequential authority
- Security approves external tool boundary
Keep exploring