List entries with optional filters.
AI agents call list_entries_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 retrieves or queries feed entries from the RSS/Atom reader backend using optional filters. It has no capacity to create, modify, delete, or execute operations—it only reads and returns data. The low severity reflects minimal blast radius: even if an AI agent abuses filters, the worst outcome is information disclosure or performance degradation, not data loss or external action.
From the tool's definition Tool name 'list_entries_tool' and description 'List entries with optional filters' indicate a retrieval operation with no side effects. The verb 'list' is a classic read operation that queries existing data without modification.
Attacks that exploit this kind of access
List entries with optional filters. 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_entries_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_entries_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_entries_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_entries_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_entries_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 →