delete_group_wiki_page

Delete a wiki page from a group

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-zereight-gitlab-mcp/delete-group-wiki-page.md

What delete_group_wiki_page does on Gitlab Mcp

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

Why delete_group_wiki_page is rated Critical

This tool irreversibly removes data (a wiki page) from a group workspace. Deletion is a destructive operation that cannot be undone through normal tool operations, making it more severe than Write (which is reversible). The impact is localized to a single wiki page rather than cascading across an entire group, preventing classification as 'critical', but it remains 'high' due to permanent data loss potential.

From the tool's definition Tool name contains 'delete'; description states 'Delete a wiki page from a group'. The action is irreversible—once a wiki page is deleted, it cannot be recovered without version control restoration.

Questions about delete_group_wiki_page

What does the delete_group_wiki_page tool do? +

Delete a wiki page from a group. It is categorised as a Destructive tool in the Gitlab Mcp 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 Mcp. 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 (@zereight/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Gitlab, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Gitlab's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.