add_rss_source
Register an RSS or Atom feed URL for monitoring. Stored in SQLite for persistent tracking. Validates the feed on add. Use fetch_rss_feeds to pull articles and build_research_digest to generate a digest of new articles.
This record as markdown: /tools/io-github-homenshum-nodebench/add-rss-source.md
What add_rss_source does on Nodebench
AI agents use add_rss_source to create or update resources in Nodebench, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodebench environment.
Why add_rss_source is rated Medium
The tool creates and persists a new RSS feed source record in a SQLite database. This is a reversible write operation (the feed can be removed or updated later). There is no irreversible deletion (would be Destructive), no code execution (would be Execute), and no financial transaction. The activity is data creation/modification, fitting the Write category.
From the tool's definition "Register an RSS or Atom feed URL for monitoring. Stored in SQLite for persistent tracking." — this stores data (a feed URL) in a SQLite database, which is a create/write operation.
Attacks that exploit this kind of access
The rule that runs add_rss_source safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_rss_source, this is the rule to start with:
add_rss_source 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every add_rss_source call is checked against it from then on.
Questions about add_rss_source
Register an RSS or Atom feed URL for monitoring. Stored in SQLite for persistent tracking. Validates the feed on add. Use fetch_rss_feeds to pull articles and build_research_digest to generate a digest of new articles. It is categorised as a Write tool in the Nodebench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nodebench MCP server in PolicyLayer and add a rule for add_rss_source: 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 Nodebench. Nothing to install.
add_rss_source 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_rss_source 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_rss_source. 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_rss_source is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue