29 tools. 17 can modify or destroy data without limits.
6 destructive tools with no built-in limits. Policy required.
Last updated:
Destructive tools (delete_access_key, delete_group, delete_role_policy) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (add_user_to_group, attach_group_policy, attach_user_policy) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
delete_access_key:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
add_user_to_group:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
get_group:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The AWS IAM MCP Server server exposes 6 destructive tools including delete_access_key, delete_group, delete_role_policy. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
The AWS IAM MCP Server server has 11 write tools including add_user_to_group, attach_group_policy, attach_user_policy. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
29 tools across 3 categories: Destructive, Read, Write. 12 are read-only. 17 can modify, create, or delete data.
One line change. Instead of running the AWS IAM MCP Server server directly, prefix it with Intercept: intercept -c aws-iam-mcp-server.yaml -- npx -y @awslabs.iam-mcp-server. Download a pre-built policy from policylayer.com/policies/aws-iam-mcp-server and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.