Critical Risk →

gitlab_delete_wiki_page

Delete a wiki page permanently. Irreversible. Requires slug. Recommended pre-check: gitlab_get_wiki_page or gitlab_list_wiki_pages.

How to control gitlab_delete_wiki_page ↓

What gitlab_delete_wiki_page does on Gitlab

AI agents call gitlab_delete_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

Why gitlab_delete_wiki_page needs a policy

The tool description explicitly states it 'Delete[s] a wiki page permanently' and is 'Irreversible', which are hallmarks of destructive operations. Wiki pages constitute documentation and knowledge artifacts that, once deleted, cannot be recovered through normal means. This falls squarely under the Destructive category rather than Write, as it is not reversible.

From the tool's definition Delete a wiki page permanently. Irreversible.

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

How to control gitlab_delete_wiki_page

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 gitlab_delete_wiki_page:

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

gitlab_delete_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.

Related tools and policies

Go deeper

Questions about gitlab_delete_wiki_page

What does the gitlab_delete_wiki_page tool do? +

Delete a wiki page permanently. Irreversible. Requires slug. Recommended pre-check: gitlab_get_wiki_page or gitlab_list_wiki_pages. 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 gitlab_delete_wiki_page? +

Register the Gitlab MCP server in PolicyLayer and add a rule for gitlab_delete_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 gitlab_delete_wiki_page? +

gitlab_delete_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 gitlab_delete_wiki_page? +

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

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

gitlab_delete_wiki_page is provided by the Gitlab MCP server (mcpland/gitlab-mcp). 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.

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

Free to start. No card required.

190 Gitlab tools catalogued and risk-classified — across an index of 43,000+ 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.