Search the feed catalog by keyword. Matches feed titles, urls, and hostnames. Returns up to 20 results with recency stats.
AI agents call search_feeds 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.
The tool retrieves information from a feed catalog without creating, modifying, executing operations, or deleting data. It is a passive search/query operation that returns search results. This is a typical Read category action with minimal risk if misused by an agent—worst case, an agent performs redundant searches.
From the tool's definition Tool description states it 'Search[es] the feed catalog by keyword' and 'Returns up to 20 results with recency stats.' This is a read-only query operation with no modification or deletion capability.
Attacks that exploit this kind of access
Search the feed catalog by keyword. Matches feed titles, urls, and hostnames. Returns up to 20 results with recency stats. 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 search_feeds: 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.
search_feeds 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 search_feeds 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 search_feeds. 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.
search_feeds 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 →