Check if AWS storage resources have encryption enabled. This tool identifies storage resources using Resource Explorer and checks if they are properly configured for data protection at rest according to AWS Well-Architected Framework Security Pillar best practices. ## Response format Returns a ...
Part of the AWS Well-Architected Security Assessment Tool MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call CheckStorageEncryption to retrieve information from AWS Well-Architected Security Assessment Tool 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 CheckStorageEncryption 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:
CheckStorageEncryption:
rules:
- action: allowSee the full AWS Well-Architected Security Assessment Tool MCP Server policy for all 6 tools.
Agents calling read-class tools like CheckStorageEncryption 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.
Check if AWS storage resources have encryption enabled. This tool identifies storage resources using Resource Explorer and checks if they are properly configured for data protection at rest according to AWS Well-Architected Framework Security Pillar best practices. ## Response format Returns a dictionary with: - region: The region that was checked - resources_checked: Total number of storage resources checked - compliant_resources: Number of resources with proper encryption - non_compliant_resources: Number of resources without proper encryption - compliance_by_service: Breakdown of compliance by service type - resource_details: Details about each resource checked - recommendations: Recommendations for improving data protection at rest ## AWS permissions required - resource-explorer-2:ListResources - Read permissions for each storage service being analyzed (s3:GetEncryptionConfiguration, etc.). It is categorised as a Read tool in the AWS Well-Architected Security Assessment Tool 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 CheckStorageEncryption. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Well-Architected Security Assessment Tool MCP Server MCP server.
CheckStorageEncryption 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 CheckStorageEncryption 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 CheckStorageEncryption. 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.
CheckStorageEncryption is provided by the AWS Well-Architected Security Assessment Tool MCP Server MCP server (awslabs.well-architected-security-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.