source_remove

A destructive tool on the Mcp Anything MCP server.

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/source-remove.md

WHAT IT DOES

What source_remove does on Mcp Anything

AI agents call source_remove 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 source_remove is rated Critical

The 'remove' verb paired with 'source' maps to destructive operations that cannot be undone. This carries significant risk if an agent misuses it to delete critical source files or code repositories. Severity is high rather than critical because the exact scope (single file, directory, or entire repository) is unclear due to lack of documentation.

From the tool's definition Tool name 'source_remove' indicates deletion or removal of source data/code without reversibility. No description provided, limiting confidence.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs source_remove 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 source_remove, this is the rule to start with:

source_remove Hidden

source_remove 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": [
    "source_remove"
  ]
}

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 source_remove call is checked against it from then on.

FAQ

Questions about source_remove

What does the source_remove tool do? +

source_remove is a destructive tool on the Mcp Anything MCP server. 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 source_remove? +

Register the Mcp Anything MCP server in PolicyLayer and add a rule for source_remove: 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 source_remove? +

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

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

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

source_remove 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 →