3 tools. 3 can modify or destroy data without limits.
3 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (finch_create_ecr_repo, finch_push_image) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (finch_build_container_image) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
finch_create_ecr_repo:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
The Finch MCP Server server has 2 write tools including finch_create_ecr_repo, finch_push_image. 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.
3 tools across 2 categories: Execute, Write. 0 are read-only. 3 can modify, create, or delete data.
One line change. Instead of running the Finch MCP Server server directly, prefix it with Intercept: intercept -c finch-mcp-server.yaml -- npx -y @awslabs.finch-mcp-server. Download a pre-built policy from policylayer.com/policies/finch-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.