Delete a release from a GitHub repository
AI agents call delete_release to permanently remove resources in Mcp Github — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a GitHub release, which cannot be undone. While not a complete data loss (the repository itself remains), deleting a release removes version artifacts, tags, and associated metadata from the release history. This is an irreversible action with significant impact on repository versioning and user access to specific release versions, warranting the Destructive category.
From the tool's definition Tool name 'delete_release' combined with description 'Delete a release from a GitHub repository' explicitly performs an irreversible deletion action.
Attacks that exploit this kind of access
Delete a release from a GitHub repository. It is categorised as a Destructive tool in the Mcp Github MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Github MCP server in PolicyLayer and add a rule for delete_release: 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 Mcp Github. Nothing to install.
delete_release 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_release 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_release. 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_release is provided by the Mcp Github MCP server (@missionsquad/mcp-github). 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 →