AI agents call get_items_by_feed_ids to retrieve information from RSS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name follows the 'get_' prefix pattern consistent with read/retrieval operations. Sibling tools like get_feeds, get_groups, get_items, get_saved_items, and get_unread_items are all read operations, and this tool fits the same pattern — fetching items filtered by feed IDs.
From the tool's definition Tool name 'get_items_by_feed_ids' and server context describing 'retrieval of feeds, groups, and items'
Documented attack patterns abuse exactly the kind of access get_items_by_feed_ids 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 get_items_by_feed_ids:
{
"version": "1",
"default": "deny",
"tools": {
"get_items_by_feed_ids": {}
}
}get_items_by_feed_ids is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_items_by_feed_ids. It is categorised as a Read tool in the RSS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RSS MCP Server MCP server in PolicyLayer and add a rule for get_items_by_feed_ids: 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.
get_items_by_feed_ids is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_items_by_feed_ids 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 get_items_by_feed_ids. 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.
get_items_by_feed_ids is provided by the RSS MCP Server MCP server (weekend-project-space/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.
8 RSS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.