Critical Risk →

delete_group_wiki_page

Delete a wiki page from a GitLab group

How to control delete_group_wiki_page ↓

AI agents call delete_group_wiki_page to permanently remove resources in Gitlab — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

The delete_group_wiki_page tool performs an irreversible deletion of group wiki content. Deletion cannot be undone without restore operations, making this a Destructive action. Severity is high because loss of documentation can disrupt team knowledge and operations, though the blast radius is typically limited to a single wiki page unless the agent is tricked into bulk deletions.

From the tool's definition Tool name contains 'delete' and description states 'Delete a wiki page from a GitLab group' — this irreversibly removes documentation content.

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_group_wiki_page"
  ]
}

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

  1. Create a free account and register Gitlab — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete_group_wiki_page tool do? +

Delete a wiki page from a GitLab group. It is categorised as a Destructive tool in the Gitlab 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 delete_group_wiki_page? +

Register the Gitlab MCP server in PolicyLayer and add a rule for delete_group_wiki_page: 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. Nothing to install.

What risk level is delete_group_wiki_page? +

delete_group_wiki_page 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 delete_group_wiki_page? +

Yes. Add a rate_limit block to the delete_group_wiki_page 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 delete_group_wiki_page completely? +

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

delete_group_wiki_page is provided by the Gitlab MCP server (yoda-digital/mcp-gitlab-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Gitlab tool call.

Deterministic rules across all 88 Gitlab tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

88 Gitlab tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.