19 tools. 5 can modify or destroy data without limits.
1 destructive tool with no built-in limits. Policy required.
Last updated:
Destructive tools (cancel_logs_insight_query) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Execute tools (execute_cwl_insights_batch, execute_log_insights_query, execute_promql_query) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
cancel_logs_insight_query:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
analyze_log_group:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The AWS Labs CloudWatch MCP Server server exposes 1 destructive tools including cancel_logs_insight_query. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
19 tools across 3 categories: Destructive, Execute, Read. 14 are read-only. 5 can modify, create, or delete data.
One line change. Instead of running the AWS Labs CloudWatch MCP Server server directly, prefix it with Intercept: intercept -c aws-labs-cloudwatch-mcp-server.yaml -- npx -y @awslabs.cloudwatch-mcp-server. Download a pre-built policy from policylayer.com/policies/aws-labs-cloudwatch-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.