Deletes a repository, organization, or environment GitHub Actions variable.
AI agents call variable-delete to permanently remove resources in Cargo — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation on GitHub Actions variables, which cannot be undone. Deletion of variables could break CI/CD pipelines, remove critical secrets or configuration, and cause operational disruption. While not directly financial or code-execution, the destructive nature of permanent variable removal and its potential to disable automation pipelines justifies 'high' severity.
From the tool's definition Tool name 'variable-delete' and description 'Deletes a repository, organization, or environment GitHub Actions variable' explicitly indicate irreversible deletion of configuration data.
Documented attack patterns abuse exactly the kind of access variable-delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cargo, and nothing reaches the server without passing your rules. This is the rule we recommend for variable-delete:
{
"version": "1",
"default": "deny",
"hide": [
"variable-delete"
]
}variable-delete 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 repository, organization, or environment GitHub Actions variable. It is categorised as a Destructive tool in the Cargo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cargo MCP server in PolicyLayer and add a rule for variable-delete: 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 Cargo. Nothing to install.
variable-delete 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 variable-delete 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 variable-delete. 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.
variable-delete is provided by the Cargo MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cargo, 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.
202 Cargo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.