GetStoredSecurityContext
AI agents call GetStoredSecurityContext to retrieve information from Amazon MQ MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves stored security context information, which is a Read operation (query/fetch with no side effects). However, the target data is security credentials or contexts, which if exposed to an AI agent could enable privilege escalation or unauthorized access—hence medium severity rather than low.
From the tool's definition Tool name 'GetStoredSecurityContext' indicates retrieval of security context data. The empty description prevents definitive classification, but the 'Get' prefix and context-retrieval semantics suggest a read operation that accesses sensitive security…
Attacks that exploit this kind of access
GetStoredSecurityContext. It is categorised as a Read tool in the Amazon MQ MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon MQ 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 Amazon MQ 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 Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.