Analyze S3 bucket usage patterns for data processing services (Glue, EMR, Athena). This tool helps identify which buckets are actively used by data processing services and which ones might be idle or underutilized. Args: ctx: The MCP context bucket_name: Optional specific bucket to anal...
Part of the Amazon Data Processing MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call analyze_s3_usage_for_data_processing to retrieve information from Amazon Data Processing MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though analyze_s3_usage_for_data_processing only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
analyze_s3_usage_for_data_processing:
rules:
- action: allow See the full Amazon Data Processing MCP Server policy for all 36 tools.
Agents calling read-class tools like analyze_s3_usage_for_data_processing have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Analyze S3 bucket usage patterns for data processing services (Glue, EMR, Athena). This tool helps identify which buckets are actively used by data processing services and which ones might be idle or underutilized. Args: ctx: The MCP context bucket_name: Optional specific bucket to analyze (None for all buckets) Returns: CallToolResult: Analysis report of S3 usage patterns. It is categorised as a Read tool in the Amazon Data Processing MCP Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for analyze_s3_usage_for_data_processing. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Amazon Data Processing MCP Server MCP server.
analyze_s3_usage_for_data_processing is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the analyze_s3_usage_for_data_processing rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the Intercept policy for analyze_s3_usage_for_data_processing. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
analyze_s3_usage_for_data_processing is provided by the Amazon Data Processing MCP Server MCP server (awslabs.aws-dataprocessing-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.