remove

Runs

SERVERSearch SOURCEDave-London/Pare

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/io-github-dave-london-pare-search/remove.md

WHAT IT DOES

What remove does on Search

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

RISK

Why remove is rated Critical

The tool name 'remove' strongly suggests deletion or irreversible removal of files or data. Given the sibling tools include file/package operations (add, add-package, archive) and the server focuses on structured code operations, this tool most likely performs destructive file removal.

From the tool's definition Tool named 'remove' with incomplete description stating 'Runs' - likely removes files or data given the name and context of a code search server offering file operations (add, archive, audit, apply, etc.)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove safely

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

remove Hidden

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

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about remove

What does the remove tool do? +

Runs. It is categorised as a Destructive tool in the Search 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? +

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

What risk level is remove? +

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

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

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

remove is provided by the Search MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Search, and thousands of servers like it.

This server

All 202 Search 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 code and CI agents →Blast radius →Tool call approval →