Delete a stored key by name.
AI agents call pqc_key_store_delete to permanently remove resources in Post-Quantum Cryptography MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes stored keys, which cannot be recovered. Misuse by an AI agent could result in loss of critical cryptographic material needed for decryption or signature verification, compromising system security and data recovery.
From the tool's definition Tool performs 'Delete a stored key by name' - explicit deletion operation that irreversibly removes cryptographic key material from storage with no undo capability.
Attacks that exploit this kind of access
Delete a stored key by name. It is categorised as a Destructive tool in the Post-Quantum Cryptography MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Post-Quantum Cryptography MCP Server MCP server in PolicyLayer and add a rule for pqc_key_store_delete: 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_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pqc_key_store_delete 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_delete. 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_delete 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 →