gitlab_delete_webhook

THE RISK

Critical Risk

Why gitlab_delete_webhook needs a policy

Deleting a webhook irreversibly removes a configured integration endpoint. This action cannot be undone and requires manual intervention to restore. While not as critical as deleting repositories or data, it disrupts CI/CD automation and external service integrations, making it a destructive operation.

From the tool's definition Tool name explicitly states 'delete_webhook' and description confirms 'Delete a webhook'. Webhooks are configured integrations that, once deleted, cannot be recovered without manual reconfiguration.

Documented attack patterns abuse exactly the kind of access gitlab_delete_webhook gives an agent:

POLICY

How to control gitlab_delete_webhook

PolicyLayer is an MCP gateway — it sits between your AI agents and GitLab MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for gitlab_delete_webhook:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "gitlab_delete_webhook"
  ]
}

gitlab_delete_webhook disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register GitLab MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GitLab MCP Server tools

Destructive gitlab_delete_cicd_variable Delete a CI/CD variable Destructive gitlab_delete_trigger_token Delete a pipeline trigger token Execute gitlab_trigger_pipeline Trigger a pipeline run Execute gitlab_test_webhook Test a webhook Write gitlab_add_group_member Add a user to a group Write gitlab_add_project_member Add a user to a project Write gitlab_add_webhook Add a new webhook to a project Write gitlab_create_cicd_variable Create a new CI/CD variable

All 42 GitLab MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in GitLab MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about gitlab_delete_webhook

What does the gitlab_delete_webhook tool do? +

Delete a webhook. It is categorised as a Destructive tool in the GitLab MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on gitlab_delete_webhook? +

Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for gitlab_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 GitLab MCP Server. Nothing to install.

What risk level is gitlab_delete_webhook? +

gitlab_delete_webhook is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit gitlab_delete_webhook? +

Yes. Add a rate_limit block to the gitlab_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.

How do I block gitlab_delete_webhook completely? +

Set action: deny in the PolicyLayer policy for gitlab_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.

What MCP server provides gitlab_delete_webhook? +

gitlab_delete_webhook is provided by the GitLab MCP Server MCP server (rifqi96/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GitLab MCP Server tool call.

Start from GitLab MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →