pki-rotate-crl
AI agents invoke pki-rotate-crl to trigger actions in Vault MCP Server (mschuchard). What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Rotating a CRL is an operational action that triggers regeneration/update of the certificate revocation list in Vault's PKI engine. This is an external operation with real effects on PKI infrastructure (affecting which certificates are considered valid/revoked). It is not purely a read, nor is it a simple write or destructive delete — it executes a rotation operation.
From the tool's definition Tool name 'pki-rotate-crl' suggests rotating a Certificate Revocation List (CRL) in the PKI secrets engine; description is empty and uninformative.
Attacks that exploit this kind of access
pki-rotate-crl. It is categorised as a Execute tool in the Vault MCP Server (mschuchard) MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vault MCP Server (mschuchard) MCP server in PolicyLayer and add a rule for pki-rotate-crl: 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-rotate-crl is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pki-rotate-crl 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-rotate-crl. 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-rotate-crl 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 →