Agent Tool and Action Boundary Review
Review what an agent can ask a host to do and how deterministic controls constrain the result. Read the tool action matrix when an agent has more than one tool or effect class.
Preconditions
Identify the agent, product user, service identity, registered tool inventory, data classifications, trust zones, and proposed effects. Obtain tool schemas and host policy from code or authoritative configuration rather than from model-visible prose alone.
Workflow
- Inventory every registered tool and action. Record owner, purpose, arguments, outputs, side effects, network destinations, data classes, credentials, and failure behavior.
- Trace authentication and authorization from the human or system principal through the host to the downstream service. Do not treat the model as an approval authority.
- Review schema constraints, canonicalization, allowlists, resource identifiers, object ownership, query limits, and server-side validation. Assume arguments can be manipulated.
- Map read, compute, draft, external write, destructive, financial, publication, deployment, and trust-decision effects.
- Review SSRF, confused-deputy, data-exfiltration, privilege-escalation, cross-tenant, and indirect prompt-injection paths.
- For consequential effects, require durable external approval where appropriate, authenticated approvers, binding of approval to exact arguments, expiration, idempotency keys, replay protection, and auditable result readback.
- Define cancellation, retry, timeout, duplicate delivery, partial failure, rollback, and emergency stop behavior.
- Test that unregistered tools remain unavailable and that skill text or retrieved content cannot expand the host tool registry or policy.
- Report findings without enabling, invoking, publishing, deploying, or changing a tool.
Routing Boundaries
- Use
review-app-security for conventional authentication, authorization, input handling, and data protection across the application.
- Use
review-agent-security for the broader model, memory, retrieval, delegation, and supply-chain threat model.
- Use
review-api-compatibility for producer and consumer compatibility rather than action authority.
Output
Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.
Return Decision, Tool inventory, Identity chain, Effect classes, Argument controls, Network and data boundaries, Approval and replay controls, Failure and recovery, Audit evidence, Findings, Required tests, and Authority still needed.
Tool Action Matrix
Create one row per registered tool and distinguish host policy from model-visible instructions.
| Field |
Required evidence |
| Tool |
Registered name, version, owner, and implementation |
| Caller |
Agent identity and authenticated product principal |
| Arguments |
Schema, validation, allowlists, ownership checks, and limits |
| Data |
Input and output classifications and tenant boundary |
| Network |
Allowed destination, redirect policy, DNS and address controls |
| Effect |
Read, compute, draft, external write, destructive, financial, publication, deployment, or trust decision |
| Approval |
Approver, exact bound arguments, expiration, and durable record |
| Replay |
Idempotency key, duplicate handling, retry, and cancellation |
| Recovery |
Rollback, compensation, partial failure, and emergency stop |
| Evidence |
Request, decision, execution, and readback audit records |
Primary resources
Experimental in-process confirmation can demonstrate interaction behavior, but it is not durable, replay-safe authorization for a production external write.
Example
Synthetic example; not an observed client result.
Input: A refund tool accepts an amount and customer ID supplied by the model.
Output: Authorization must be enforced by the tool using the authenticated actor and allowed account scope; model-supplied identifiers are not permission.
1---2name: review-agent-tools3description: "Reviews agent tool permissions when asked what an agent can access, whether a tool call is safe, or how retries affect writes; tool descriptions cannot grant authority."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/review-agent-tools7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-quality"10 invocation: "implicit"11 provenance: "original"12 risk_class: "read-only"13---1415# Agent Tool and Action Boundary Review1617Review what an agent can ask a host to do and how deterministic controls constrain the result. Read [the tool action matrix](#tool-action-matrix) when an agent has more than one tool or effect class.1819## Preconditions2021Identify the agent, product user, service identity, registered tool inventory, data classifications, trust zones, and proposed effects. Obtain tool schemas and host policy from code or authoritative configuration rather than from model-visible prose alone.2223## Workflow24251. Inventory every registered tool and action. Record owner, purpose, arguments, outputs, side effects, network destinations, data classes, credentials, and failure behavior.262. Trace authentication and authorization from the human or system principal through the host to the downstream service. Do not treat the model as an approval authority.273. Review schema constraints, canonicalization, allowlists, resource identifiers, object ownership, query limits, and server-side validation. Assume arguments can be manipulated.284. Map read, compute, draft, external write, destructive, financial, publication, deployment, and trust-decision effects.295. Review SSRF, confused-deputy, data-exfiltration, privilege-escalation, cross-tenant, and indirect prompt-injection paths.306. For consequential effects, require durable external approval where appropriate, authenticated approvers, binding of approval to exact arguments, expiration, idempotency keys, replay protection, and auditable result readback.317. Define cancellation, retry, timeout, duplicate delivery, partial failure, rollback, and emergency stop behavior.328. Test that unregistered tools remain unavailable and that skill text or retrieved content cannot expand the host tool registry or policy.339. Report findings without enabling, invoking, publishing, deploying, or changing a tool.3435## Routing Boundaries3637- Use `review-app-security` for conventional authentication, authorization, input handling, and data protection across the application.38- Use `review-agent-security` for the broader model, memory, retrieval, delegation, and supply-chain threat model.39- Use `review-api-compatibility` for producer and consumer compatibility rather than action authority.4041## Output4243Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.4445Return `Decision`, `Tool inventory`, `Identity chain`, `Effect classes`, `Argument controls`, `Network and data boundaries`, `Approval and replay controls`, `Failure and recovery`, `Audit evidence`, `Findings`, `Required tests`, and `Authority still needed`.4647## Tool Action Matrix4849Create one row per registered tool and distinguish host policy from model-visible instructions.5051| Field | Required evidence |52| --- | --- |53| Tool | Registered name, version, owner, and implementation |54| Caller | Agent identity and authenticated product principal |55| Arguments | Schema, validation, allowlists, ownership checks, and limits |56| Data | Input and output classifications and tenant boundary |57| Network | Allowed destination, redirect policy, DNS and address controls |58| Effect | Read, compute, draft, external write, destructive, financial, publication, deployment, or trust decision |59| Approval | Approver, exact bound arguments, expiration, and durable record |60| Replay | Idempotency key, duplicate handling, retry, and cancellation |61| Recovery | Rollback, compensation, partial failure, and emergency stop |62| Evidence | Request, decision, execution, and readback audit records |6364### Primary resources6566- [Google ADK safety and security](https://adk-labs.github.io/adk-docs/safety/)67- [Google ADK tool confirmation](https://adk-labs.github.io/adk-docs/tools-custom/confirmation/)68- [NIST concept paper on software agent identity and authority](https://www.nist.gov/news-events/news/2026/02/new-concept-paper-identity-and-authority-software-agents)6970Experimental in-process confirmation can demonstrate interaction behavior, but it is not durable, replay-safe authorization for a production external write.7172## Example7374Synthetic example; not an observed client result.7576Input: A refund tool accepts an amount and customer ID supplied by the model.7778Output: Authorization must be enforced by the tool using the authenticated actor and allowed account scope; model-supplied identifiers are not permission.