List RSS feed sources with pagination and filtering. Get feed IDs, titles, categories, and URLs. Use to: discover available sources, find exact feed names for filtering, browse by category. Returns feeds sorted by favorite status (favorites first), then alphabetically. With 518+ feeds, pagination...
AI agents call get_sources to retrieve information from MCP RSS without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves and lists data from RSS feed sources with no side effects. It enables discovery and browsing of feed metadata but does not modify, delete, or execute any operations. The low severity reflects minimal blast radius—misuse would only result in viewing feed metadata that is already intended to be discoverable.
From the tool's definition Tool 'get_sources' is described as 'List RSS feed sources with pagination and filtering' and returns 'feed IDs, titles, categories, and URLs.' The stated purposes are 'discover available sources, find exact feed names for filtering, browse by category.' No…
Attacks that exploit this kind of access
List RSS feed sources with pagination and filtering. Get feed IDs, titles, categories, and URLs. Use to: discover available sources, find exact feed names for filtering, browse by category. Returns feeds sorted by favorite status (favorites first), then alphabetically. With 518+ feeds, pagination is REQUIRED (default: 50/page). Response includes total count. Call before using source filter in other tools. It is categorised as a Read tool in the MCP RSS MCP Server, which means it retrieves data without modifying state.
Register the MCP RSS MCP server in PolicyLayer and add a rule for get_sources: 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 RSS. Nothing to install.
get_sources 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_sources 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_sources. 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_sources is provided by the MCP RSS MCP server (ronnycoding/my_mcp_rss). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_sources is one line of MCP RSS's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →