Critical Risk →

remove-wiki

Removes a wiki from the MCP resources. Clears any cached credentials and license metadata for the wiki. Fails if the specified wiki is currently active; call set-wiki to switch to a different wiki first.

Risk signalsAccepts URL/endpoint input (uri)

Part of the MediaWiki MCP Server server.

remove-wiki can permanently delete data in MediaWiki MCP Server, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE MEDIAWIKI MCP SERVER →

Free to start. No card required.

AI agents may call remove-wiki to permanently remove or destroy resources in MediaWiki MCP Server. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call remove-wiki in a loop, permanently destroying resources in MediaWiki MCP Server. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove-wiki"
  ]
}

See the full MediaWiki MCP Server policy for all 22 tools.

Get this rule live on your own MediaWiki MCP Server server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MEDIAWIKI MCP SERVER →

View all 22 tools →

These attack patterns abuse exactly the kind of access remove-wiki gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so remove-wiki only ever does what you allow.

SECURE MEDIAWIKI MCP SERVER →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the remove-wiki tool do? +

Removes a wiki from the MCP resources. Clears any cached credentials and license metadata for the wiki. Fails if the specified wiki is currently active; call set-wiki to switch to a different wiki first.. It is categorised as a Destructive tool in the MediaWiki MCP Server 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 remove-wiki? +

Register the MediaWiki MCP Server MCP server in PolicyLayer and add a rule for remove-wiki: 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 MediaWiki MCP Server. Nothing to install.

What risk level is remove-wiki? +

remove-wiki 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 remove-wiki? +

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

Set action: deny in the PolicyLayer policy for remove-wiki. 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 remove-wiki? +

remove-wiki is provided by the MediaWiki MCP Server MCP server (@professional-wiki/mediawiki-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MediaWiki MCP Server tool call.

Deterministic rules across all 22 MediaWiki MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.