Delete a credential from the store
AI agents call delete_credential to permanently remove resources in Credential Manager MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of credentials cannot be undone and permanently removes authentication material from storage. While not directly financial, the loss of API credentials can cause severe operational harm (access loss, service disruption) and is irreversible. Destructive is the appropriate category as it is the most severe action among write, execute, and destructive.
From the tool's definition Tool name is 'delete_credential' with description 'Delete a credential from the store' — the verb 'delete' explicitly indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a credential from the store. It is categorised as a Destructive tool in the Credential Manager MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Credential Manager MCP Server MCP server in PolicyLayer and add a rule for delete_credential: 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 Credential Manager MCP Server. Nothing to install.
delete_credential 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 delete_credential 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 delete_credential. 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.
delete_credential is provided by the Credential Manager MCP Server MCP server (mclamee/credential-manager-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 →