AI agents call delete_secret to permanently remove resources in Keyshade — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes secrets from a secrets management platform. Deletion of secrets is irreversible and represents a loss of access to critical authentication material, credentials, or sensitive data. While not directly financial or causing external system damage, the destruction of secret values could result in service unavailability, broken deployments, or security breaches if misused.
From the tool's definition Tool name is 'delete_secret' and description states it 'Deletes a secret from a project'. The verb 'Deletes' combined with the operation of removing a secret—which is sensitive security material—constitutes an irreversible action.
Documented attack patterns abuse exactly the kind of access delete_secret gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Keyshade, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_secret:
{
"version": "1",
"default": "deny",
"hide": [
"delete_secret"
]
}delete_secret disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Deletes a secret from a project. It is categorised as a Destructive tool in the Keyshade MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Keyshade 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 Keyshade. 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 Keyshade MCP server (keyshade-xyz/keyshade-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Keyshade, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
44 Keyshade tools catalogued and risk-classified — across an index of 43,000+ MCP servers.