Critical Risk →

delete_variable

Deletes a variable from a project

How to control delete_variable ↓

What delete_variable does on Keyshade

AI agents call delete_variable 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.

Critical Risk

Why delete_variable needs a policy

Deletion of variables is an irreversible destructive action that cannot be undone. Variables in a secrets management platform store configuration and sensitive data; deleting them removes them permanently from the project. This falls squarely into the Destructive category, which takes precedence over Write (which is reversible).

From the tool's definition Tool name is 'delete_variable' and description states it 'Deletes a variable from a project'. The verb 'delete' and the action of removing a variable is irreversible.

Documented attack patterns abuse exactly the kind of access delete_variable gives an agent:

How to control delete_variable

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_variable:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_variable"
  ]
}

delete_variable disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Keyshade — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_variable

What does the delete_variable tool do? +

Deletes a variable 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.

How do I enforce a policy on delete_variable? +

Register the Keyshade MCP server in PolicyLayer and add a rule for delete_variable: 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.

What risk level is delete_variable? +

delete_variable is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_variable? +

Yes. Add a rate_limit block to the delete_variable 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.

How do I block delete_variable completely? +

Set action: deny in the PolicyLayer policy for delete_variable. 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.

What MCP server provides delete_variable? +

delete_variable 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.

Enforce policy on every Keyshade tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.