36 tools. 32 can modify or destroy data without limits.
32 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (add_inline_policy, create_data_processing_role, manage_aws_athena_data_catalogs) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
add_inline_policy:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
analyze_s3_usage_for_data_processing:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Amazon Data Processing MCP Server server has 32 write tools including add_inline_policy, create_data_processing_role, manage_aws_athena_data_catalogs. 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.
36 tools across 2 categories: Read, Write. 4 are read-only. 32 can modify, create, or delete data.
One line change. Instead of running the Amazon Data Processing MCP Server server directly, prefix it with Intercept: intercept -c amazon-data-processing-mcp-server.yaml -- npx -y @awslabs.aws-dataprocessing-mcp-server. Download a pre-built policy from policylayer.com/policies/amazon-data-processing-mcp-server and adjust the limits to match your use case.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.