Low Risk

list_s3_buckets

List S3 buckets that have 'glue' in their name and are in the specified region. This tool helps identify S3 buckets commonly used for data processing workflows, particularly those related to AWS Glue operations. It provides usage statistics and idle time information to help with resource managem...

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 list_s3_buckets 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 list_s3_buckets 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.

amazon-data-processing-mcp-server.yaml
tools:
  list_s3_buckets:
    rules:
      - action: allow

See the full Amazon Data Processing MCP Server policy for all 36 tools.

Tool Name list_s3_buckets
Category Read
Risk Level Low

View all 36 tools →

Agents calling read-class tools like list_s3_buckets have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the list_s3_buckets tool do? +

List S3 buckets that have 'glue' in their name and are in the specified region. This tool helps identify S3 buckets commonly used for data processing workflows, particularly those related to AWS Glue operations. It provides usage statistics and idle time information to help with resource management. ## Requirements - Valid AWS credentials with permissions to list S3 buckets - S3:ListAllMyBuckets permission ## Response Information The response includes bucket name, creation date, region, object count, last modified date, and idle time analysis. ## Usage Tips - Use this tool to find existing data processing buckets before creating new ones - Monitor idle buckets that haven't been accessed for 90+ days - Verify bucket regions match your data processing service regions - Check object counts to understand bucket usage patterns Args: ctx: The MCP context region: AWS region to filter buckets by Returns: CallToolResult: Information about matching S3 buckets. It is categorised as a Read tool in the Amazon Data Processing MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_s3_buckets? +

Add a rule in your Intercept YAML policy under the tools section for list_s3_buckets. 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.

What risk level is list_s3_buckets? +

list_s3_buckets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_s3_buckets? +

Yes. Add a rate_limit block to the list_s3_buckets 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.

How do I block list_s3_buckets completely? +

Set action: deny in the Intercept policy for list_s3_buckets. 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.

What MCP server provides list_s3_buckets? +

list_s3_buckets 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.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.