List all feeds with unread counts.
AI agents call list_feeds_tool to retrieve information from MCP Feed Reader without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation to retrieve and display feed information. It has no side effects, does not create, modify, or delete data, and does not execute external operations or move money. The blast radius of misuse is minimal—an AI agent could only retrieve information that already exists in the feed reader's database.
From the tool's definition Tool name 'list_feeds_tool' and description 'List all feeds with unread counts' indicate a retrieval operation that queries and returns feed metadata without modifying any data.
Attacks that exploit this kind of access
List all feeds with unread counts. It is categorised as a Read tool in the MCP Feed Reader MCP Server, which means it retrieves data without modifying state.
Register the MCP Feed Reader MCP server in PolicyLayer and add a rule for list_feeds_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.
list_feeds_tool 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 list_feeds_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 list_feeds_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.
list_feeds_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 →