contribute_delete-tool

THE RISK

Critical Risk

Why contribute_delete-tool needs a policy

This tool irreversibly deletes data (a tool configuration) from a shared community resource. Even though deletion may be restricted to config owners or tool creators (as the truncated description suggests), the action cannot be undone and removes data from the hub. This is a destructive operation with potential impact on the community's available tools.

From the tool's definition Tool name contains 'delete' and description states 'Delete a specific tool from a WebMCP Hub config.' The action irreversibly removes a tool contribution from a shared community hub.

Documented attack patterns abuse exactly the kind of access contribute_delete-tool gives an agent:

POLICY

How to control contribute_delete-tool

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "contribute_delete-tool"
  ]
}

contribute_delete-tool disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register MoltBrowser MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MoltBrowser MCP Server tools

Execute hub_execute Execute a pre-configured hub tool for the current site. After navigating, the response wil Execute click-compose-button Click the compose/new tweet button to open the tweet editor Execute click-post-button Click the Post button to submit the tweet Write contribute_vote-on-tool Upvote or downvote a tool within a WebMCP Hub config. Each user gets one vote per tool — v Write fill-search Fill the search input field with a query. After calling this, use browser_press_key({ key: Write fill-tweet-text Fill the tweet text area with content Read get-article Get the main article text Read get-posts Get all visible posts on the page

All 9 MoltBrowser MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in MoltBrowser MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about contribute_delete-tool

What does the contribute_delete-tool tool do? +

Delete a specific tool from a WebMCP Hub config. The config owner or the tool\. It is categorised as a Destructive tool in the MoltBrowser 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 contribute_delete-tool? +

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

What risk level is contribute_delete-tool? +

contribute_delete-tool 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 contribute_delete-tool? +

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

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

contribute_delete-tool is provided by the MoltBrowser MCP Server MCP server (joakim-sael/moltbrowser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MoltBrowser MCP Server tool call.

Start from MoltBrowser MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →