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