doc_remove_element

Remove an element from the document.

SERVERMcp Anything SOURCEZaymadkid/mcp-anything

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-anything/doc-remove-element.md

WHAT IT DOES

What doc_remove_element does on Mcp Anything

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

RISK

Why doc_remove_element is rated Critical

Removal of document elements is a destructive operation that cannot be undone unless the document system has built-in undo capabilities (not mentioned). An AI agent calling this tool carelessly could permanently erase critical content. This is more severe than Write (which is reversible) and justifies the Destructive classification.

From the tool's definition Tool name includes 'remove' and description states 'Remove an element from the document' — this irreversibly deletes content from a document.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs doc_remove_element safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For doc_remove_element, this is the rule to start with:

doc_remove_element Hidden

doc_remove_element is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "doc_remove_element"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Anything, apply this rule, and every doc_remove_element call is checked against it from then on.

FAQ

Questions about doc_remove_element

What does the doc_remove_element tool do? +

Remove an element from the document. It is categorised as a Destructive tool in the Mcp Anything 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 doc_remove_element? +

Register the Mcp Anything MCP server in PolicyLayer and add a rule for doc_remove_element: 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 Mcp Anything. Nothing to install.

What risk level is doc_remove_element? +

doc_remove_element 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 doc_remove_element? +

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

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

doc_remove_element is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Anything, and thousands of servers like it.

This server

All 261 Mcp Anything tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →