variable-delete
Deletes a repository, organization, or environment GitHub Actions variable.
This record as markdown: /tools/io-github-dave-london-github/variable-delete.md
What variable-delete does on Github
AI agents call variable-delete to permanently remove resources in Github, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why variable-delete is rated Critical
This tool permanently removes GitHub Actions variables, which cannot be undone. While the blast radius is limited to configuration rather than code or credentials themselves, deletion of environment or organization variables could disrupt CI/CD workflows or break dependent processes.
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.
Attacks that exploit this kind of access
The rule that runs variable-delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Github, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For variable-delete, this is the rule to start with:
variable-delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Github, apply this rule, and every variable-delete call is checked against it from then on.
Questions about variable-delete
Deletes a repository, organization, or environment GitHub Actions variable. It is categorised as a Destructive tool in the Github MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Github 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 Github. 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 Github MCP server (@paretools/github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Github, and thousands of servers like it.
Across the catalogue