List all stored keys with metadata
AI agents call pqc_key_store_list to retrieve information from Post-Quantum Cryptography MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads cryptographic key metadata without side effects. Although keys are sensitive, merely listing their metadata (such as key IDs, creation dates, or algorithm types) does not expose the key material itself or enable misuse. An AI agent listing keys poses minimal risk compared to tools that generate, delete, or use keys.
From the tool's definition Tool is described as 'List all stored keys with metadata' — a query/enumeration operation with no modification or destruction of data. The verb 'list' is a passive retrieval operation.
Attacks that exploit this kind of access
List all stored keys with metadata. It is categorised as a Read tool in the Post-Quantum Cryptography MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Post-Quantum Cryptography MCP Server MCP server in PolicyLayer and add a rule for pqc_key_store_list: 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 Post-Quantum Cryptography MCP Server. Nothing to install.
pqc_key_store_list 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 pqc_key_store_list 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 pqc_key_store_list. 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.
pqc_key_store_list is provided by the Post-Quantum Cryptography MCP Server MCP server (scottdhughes/post-quantum-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 →