CheckStorageEncryption
AI agents call CheckStorageEncryption to retrieve information from AWS IoT SiteWise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Given the empty description, classification relies on the tool name. 'Check' typically implies inspection or verification without modification. In AWS security contexts, such tools commonly retrieve and report on encryption configuration state. The lack of action verbs suggesting modification, deletion, or execution keeps this in the Read category.
From the tool's definition Tool name 'CheckStorageEncryption' suggests a query or audit operation that retrieves encryption status information. The absence of verbs like 'enable', 'disable', 'update', or 'delete' indicates a read-only assessment.
Attacks that exploit this kind of access
CheckStorageEncryption. It is categorised as a Read tool in the AWS IoT SiteWise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for CheckStorageEncryption: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches AWS IoT SiteWise MCP Server. Nothing to install.
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 PolicyLayer 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 PolicyLayer 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 IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.