List recent entries across all feeds, paginated. Use sort_by=
AI agents call list_entries to retrieve information from Feedbagel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays feed entries without altering data, triggering external actions, or affecting system state. It is a straightforward read operation. Severity is low because listing entries poses minimal risk even if called inappropriately by an agent—it only exposes data the user is already subscribed to.
From the tool's definition Tool description states 'List recent entries across all feeds, paginated' - a retrieval operation with no modification, deletion, or side effects. The verb 'list' and context of pagination for feed entries confirm this is a query operation.
Attacks that exploit this kind of access
List recent entries across all feeds, paginated. Use sort_by=. It is categorised as a Read tool in the Feedbagel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Feedbagel MCP Server MCP server in PolicyLayer and add a rule for list_entries: 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 Feedbagel MCP Server. Nothing to install.
list_entries 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 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. 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 is provided by the Feedbagel MCP Server MCP server (prototypr/feedbagel-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 →