AI agents call fetch_by_category to retrieve information from Rss Feeds without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves RSS feed blog content filtered by predefined categories. It performs a query operation that returns data without creating, modifying, deleting, or executing any external operations. The fixed category list prevents arbitrary execution. Misuse would result in information disclosure only, with minimal blast radius.
From the tool's definition Tool description states 'Fetch blogs from a specific category' - the verb 'fetch' indicates data retrieval with no modification or deletion. The specified categories (seo, content, social, email, analytics, crm, news) are read-only content queries.
Attacks that exploit this kind of access
Fetch blogs from a specific category (seo, content, social, email, analytics, crm, news). It is categorised as a Read tool in the Rss Feeds MCP Server, which means it retrieves data without modifying state.
Register the Rss Feeds MCP server in PolicyLayer and add a rule for fetch_by_category: 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.
fetch_by_category 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 fetch_by_category 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 fetch_by_category. 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.
fetch_by_category 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 →