GetStoredSecurityContext
AI agents call GetStoredSecurityContext to retrieve information from Awslabs Valkey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name uses the 'Get' prefix, which typically indicates a read operation that retrieves data. However, security context data may be sensitive (containing credentials, permissions, or authentication tokens), which elevates severity to medium despite the read-only nature. The empty description reduces confidence as we cannot verify the exact scope of what is retrieved or how the data is used.
From the tool's definition Tool name 'GetStoredSecurityContext' suggests retrieval of security context data. No description provided, but 'Get' prefix indicates a read operation that queries or retrieves existing data without modification.
Attacks that exploit this kind of access
GetStoredSecurityContext. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Valkey 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 Awslabs Valkey. 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 Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.