Critical Risk →

replace_rule_delete

replace_rule_delete

How to control replace_rule_delete ↓

What replace_rule_delete does on Legado

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

Critical Risk

Why replace_rule_delete needs a policy

The tool name strongly implies deletion of a replace rule, which is an irreversible destructive action. The naming convention on this server is consistent: 'book_delete' deletes books, so 'replace_rule_delete' deletes replace rules. Description is empty, lowering confidence slightly, but the pattern is clear.

From the tool's definition Tool name 'replace_rule_delete' contains 'delete', indicating irreversible removal of a replace rule. Sibling tools follow a pattern where '_delete' suffix (e.g., 'book_delete') means deletion.

Documented attack patterns abuse exactly the kind of access replace_rule_delete gives an agent:

How to control replace_rule_delete

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "replace_rule_delete"
  ]
}

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

  1. Create a free account and register Legado — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about replace_rule_delete

What does the replace_rule_delete tool do? +

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

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

What risk level is replace_rule_delete? +

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

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

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

replace_rule_delete is provided by the Legado MCP server (joestar817/legado-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 Legado tool call.

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

Free to start. No card required.

31 Legado tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.