Delete a group wiki page permanently. Irreversible. Requires group_id and slug. Recommended pre-check: gitlab_get_group_wiki_page or gitlab_list_group_wiki_pages.
AI agents call gitlab_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.
This tool permanently removes data with no undo capability. While not a financial operation and not code execution, the irreversible deletion of wiki content makes it Destructive rather than Write.
From the tool's definition Tool description explicitly states 'Delete a group wiki page permanently' and 'Irreversible', indicating data cannot be recovered once removed.
Documented attack patterns abuse exactly the kind of access gitlab_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 gitlab_delete_group_wiki_page:
{
"version": "1",
"default": "deny",
"hide": [
"gitlab_delete_group_wiki_page"
]
} gitlab_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.
Free to start. No card required.
Delete a group wiki page permanently. Irreversible. Requires group_id and slug. Recommended pre-check: gitlab_get_group_wiki_page or gitlab_list_group_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.
Register the Gitlab MCP server in PolicyLayer and add a rule for gitlab_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.
gitlab_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.
Yes. Add a rate_limit block to the gitlab_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.
Set action: deny in the PolicyLayer policy for gitlab_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.
gitlab_delete_group_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.
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.