AI agents call delete_project_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 wiki page content, which cannot be undone without manual intervention or version control recovery. The destructive nature of deleting wiki pages—loss of documentation and project knowledge—makes this a high-severity risk if misused by an AI agent. Categorized as Destructive rather than Write because the action is irreversible.
From the tool's definition Tool name contains 'delete' and description states 'Delete a wiki page from a GitLab project', indicating irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_project_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_project_wiki_page:
{
"version": "1",
"default": "deny",
"hide": [
"delete_project_wiki_page"
]
}delete_project_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 wiki page from a GitLab project. 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 delete_project_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.
delete_project_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 delete_project_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 delete_project_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.
delete_project_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.
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.