AI agents use add_subscription to create or update resources in RSS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RSS MCP Server environment.
This tool creates or adds a new subscription record, which is a reversible modification of data. It does not delete, execute code, or move money. The 'medium' severity reflects that while subscription additions are generally safe, an agent could add malicious feeds or spam feeds to a user's reader, degrading user experience and potentially exposing them to unwanted content.
From the tool's definition Tool name 'add_subscription' and description 'Adds a new feed subscription' indicate creation of a new data object (feed subscription) in the RSS reader system.
Documented attack patterns abuse exactly the kind of access add_subscription gives an agent:
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 add_subscription:
{
"version": "1",
"default": "deny",
"tools": {
"add_subscription": {
"limits": [
{
"counter": "add_subscription_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} add_subscription stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Adds a new feed subscription. It is categorised as a Write tool in the RSS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RSS MCP Server MCP server in PolicyLayer and add a rule for add_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.
add_subscription is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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.
Set action: deny in the PolicyLayer policy for add_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.
add_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.
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.