Delete a secret
AI agents call delete_secret to permanently remove resources in Secr — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes secrets, which cannot be undone. Secrets often contain sensitive credentials, API keys, and authentication tokens. Unauthorized or accidental deletion could break application functionality, expose systems to compromise if backup secrets are compromised, or lock out legitimate users. The irreversible nature and high-value target (secrets) make this critical severity.
From the tool's definition Tool name is 'delete_secret' with description 'Delete a secret'. The action is irreversible deletion of secrets data.
Attacks that exploit this kind of access
Delete a secret. It is categorised as a Destructive tool in the Secr MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Secr MCP server in PolicyLayer and add a rule for delete_secret: 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 Secr. Nothing to install.
delete_secret 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_secret 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_secret. 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_secret is provided by the Secr MCP server (secr-dev/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 →