Critical Risk →

rss_source_delete_many

rss_source_delete_many

How to control rss_source_delete_many ↓

What rss_source_delete_many does on Legado

AI agents call rss_source_delete_many 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 rss_source_delete_many needs a policy

This tool performs irreversible deletion of multiple RSS source records. Even without a description, the name unambiguously indicates a destructive action that cannot be undone. The bulk nature ('many') amplifies the blast radius. This is more severe than Write operations and falls squarely into the Destructive category.

From the tool's definition Tool name 'rss_source_delete_many' explicitly indicates deletion of multiple RSS sources. The 'delete' operation combined with 'many' suggests bulk irreversible removal of data.

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

How to control rss_source_delete_many

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 rss_source_delete_many:

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

rss_source_delete_many 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 rss_source_delete_many

What does the rss_source_delete_many tool do? +

rss_source_delete_many. 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 rss_source_delete_many? +

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

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

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

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

rss_source_delete_many 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.