Elimina un webhook de un repositorio
AI agents call delete_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.
Webhook deletion is an irreversible action that cannot be undone without recreating the webhook. This removes a repository integration point and could disrupt CI/CD pipelines, notifications, or other automated workflows dependent on that webhook. While not as critical as deleting code or data, it is a destructive operation affecting repository infrastructure.
From the tool's definition delete_webhook - the tool name explicitly uses 'delete', and the description 'Elimina un webhook de un repositorio' (Spanish: 'Deletes a webhook from a repository') confirms irreversible removal of a webhook configuration.
Attacks that exploit this kind of access
Elimina un webhook de un repositorio. 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_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_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_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_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_webhook is provided by the Mcp Github MCP server (pblarismendi/mcp-github-server). 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 →