Add an RSS/Atom feed by URL, optionally assign to a category.
AI agents use add_feed_tool to create or update resources in MCP Feed Reader — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Feed Reader environment.
This tool creates new data (feed subscriptions) in a reversible manner. Users can add feeds and later delete them, making this a Write operation rather than Destructive. The blast radius is minimal—adding a feed does not compromise system security, corrupt data, or cause cascading damage. Severity is low because the worst outcome is feed clutter or noise in the feed reader.
From the tool's definition Tool name 'add_feed_tool' and description 'Add an RSS/Atom feed by URL, optionally assign to a category' indicate creation of new feed records in the SQLite backend.
Attacks that exploit this kind of access
Add an RSS/Atom feed by URL, optionally assign to a category. It is categorised as a Write tool in the MCP Feed Reader MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Feed Reader MCP server in PolicyLayer and add a rule for add_feed_tool: 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 MCP Feed Reader. Nothing to install.
add_feed_tool 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_tool 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_tool. 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_tool is provided by the MCP Feed Reader MCP server (pypi:mcp-feed-reader-crunchtools). 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 →