Delete a webhook from a repository
AI agents call delete_repository_webhook 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 deletes webhook configuration, which is a permanent and irreversible action. Unlike writes that modify data reversibly, deletion of webhooks removes infrastructure integration points that cannot be undone programmatically. The impact is high because webhooks often control critical CI/CD pipelines, notifications, and automations; removing them can break automated workflows.
From the tool's definition 'Delete a webhook from a repository' — the tool performs an irreversible deletion operation on repository infrastructure (webhooks). Once deleted, the webhook configuration cannot be recovered without manual reconfiguration.
Attacks that exploit this kind of access
Delete a webhook from a 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_repository_webhook: 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_repository_webhook 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_repository_webhook 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_repository_webhook. 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_repository_webhook 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 →