List all stored keys.
AI agents call list_keys to retrieve information from Store MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that queries and returns information about available keys in the key-value store. It has no side effects, does not modify data, and poses minimal risk if misused by an AI agent. The primary concern would be information disclosure of key names, which is relatively low severity in a key-value store context.
From the tool's definition Tool name 'list_keys' and description 'List all stored keys' indicate a retrieval operation that returns metadata about stored data without modifying or deleting anything.
Attacks that exploit this kind of access
List all stored keys. It is categorised as a Read tool in the Store MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Store MCP Server MCP server in PolicyLayer and add a rule for list_keys: 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 Store MCP Server. Nothing to install.
list_keys 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 list_keys 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 list_keys. 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.
list_keys is provided by the Store MCP Server MCP server (mariano-cecowski/store_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →