AI agents use add_feed to create or update resources in Rss Feeds — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rss Feeds environment.
Adding an RSS feed creates or modifies the system's feed configuration. This is a Write action (creates data reversibly) rather than Read (no side effects) or Destructive (cannot be undone). Severity is low because misconfiguration of RSS feeds poses minimal risk—feeds can be removed, and RSS content is typically public. No code execution, financial impact, or irreversible data loss is involved.
From the tool's definition Tool name 'add_feed' and description 'Add a new RSS feed' indicate creation of a new configuration entry. This is a reversible write operation—the feed can be removed (as evidenced by the sibling 'remove_feed' tool).
Attacks that exploit this kind of access
Add a new RSS feed with optional category. It is categorised as a Write tool in the Rss Feeds MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rss Feeds MCP server in PolicyLayer and add a rule for add_feed: 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 Feeds. Nothing to install.
add_feed 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_feed 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_feed. 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_feed is provided by the Rss Feeds MCP server (lionkiii/rss-feeds-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →