Critical Risk →

wiki_delete_page

Archive a wiki page (soft delete). Sets status to

How to control wiki_delete_page ↓

What wiki_delete_page does on Shellgate

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

Critical Risk

Why wiki_delete_page needs a policy

Although described as 'soft delete' (suggesting potential recovery), the tool removes wiki pages from normal access and is categorized as destructive because: (1) deletion/archival of data is irreversible from the user's perspective, (2) the tool's primary effect is to eliminate accessible content, and (3) misuse by an AI agent could result in loss of critical documentation or knowledge bases.

From the tool's definition Tool name 'wiki_delete_page' and description 'Archive a wiki page (soft delete)' indicates irreversible removal of wiki content from active access, even if technically recoverable via archive.

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

How to control wiki_delete_page

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

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

wiki_delete_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 Shellgate — 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 wiki_delete_page

What does the wiki_delete_page tool do? +

Archive a wiki page (soft delete). Sets status to. It is categorised as a Destructive tool in the Shellgate 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 wiki_delete_page? +

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

What risk level is wiki_delete_page? +

wiki_delete_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 wiki_delete_page? +

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

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

wiki_delete_page is provided by the Shellgate MCP server (matthiastjong/shellgate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Shellgate tool call.

Start from Shellgate, 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.

31 Shellgate 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.