pki-delete-root-ca
AI agents call pki-delete-root-ca to permanently remove resources in Vault MCP Server (mschuchard) — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a root CA is irreversible and has extreme consequences: invalidating all certificates issued by that CA, breaking trust chains, and potentially rendering dependent systems non-functional. This meets the Destructive category definition ('irreversibly deletes or overwrites data, or actions that cannot be undone').
From the tool's definition Tool name 'pki-delete-root-ca' explicitly indicates deletion of a root Certificate Authority. Vault PKI backend documentation shows this operation permanently removes the root CA certificate and cannot be reversed.
Attacks that exploit this kind of access
pki-delete-root-ca. It is categorised as a Destructive tool in the Vault MCP Server (mschuchard) MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vault MCP Server (mschuchard) MCP server in PolicyLayer and add a rule for pki-delete-root-ca: 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 Vault MCP Server (mschuchard). Nothing to install.
pki-delete-root-ca 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 pki-delete-root-ca 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 pki-delete-root-ca. 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.
pki-delete-root-ca is provided by the Vault MCP Server (mschuchard) MCP server (mschuchard/vault-mcp-server). 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 →