GetStoredSecurityContext
AI agents call GetStoredSecurityContext 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.
The tool appears to retrieve/query stored security context information based on its naming convention. 'Get' operations are characteristic of Read category tools that retrieve data without modifying state. However, the empty description prevents high confidence assessment of its exact scope and whether it might access sensitive credentials or permissions that could elevate severity.
From the tool's definition Tool name 'GetStoredSecurityContext' indicates retrieval of security context data; 'Get' is a read operation pattern. The empty description limits confidence.
Attacks that exploit this kind of access
GetStoredSecurityContext. 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 GetStoredSecurityContext: 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.
GetStoredSecurityContext 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 GetStoredSecurityContext 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 GetStoredSecurityContext. 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.
GetStoredSecurityContext 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.