Critical Risk →

delete_subscription

Deletes one or more feed subscriptions.

How to control delete_subscription ↓

What delete_subscription does on RSS MCP Server

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

Critical Risk

Why delete_subscription needs a policy

Deleting feed subscriptions is an irreversible action that removes user data permanently. Once deleted, the subscription and any associated metadata are lost. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' Severity is high because an agent could inadvertently remove many subscriptions if given broad instruction, affecting the user's…

From the tool's definition Tool name 'delete_subscription' with description 'Deletes one or more feed subscriptions' uses the verb 'deletes' which indicates irreversible removal of data.

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

How to control delete_subscription

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

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

delete_subscription 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 RSS MCP Server — 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 delete_subscription

What does the delete_subscription tool do? +

Deletes one or more feed subscriptions. It is categorised as a Destructive tool in the RSS MCP Server 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 delete_subscription? +

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

What risk level is delete_subscription? +

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

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

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

delete_subscription is provided by the RSS MCP Server MCP server (xueli-sherryli/rss-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 RSS MCP Server tool call.

Start from RSS MCP Server, 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.

34 RSS MCP Server 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.