AI agents call get_feed_items to retrieve information from Noapi Google Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries feed items with no indication of modification, deletion, or side effects. It's a basic data retrieval operation. Despite the empty description reducing confidence slightly, the naming convention and server context strongly suggest a Read operation. Low severity because feed retrieval has minimal blast radius.
From the tool's definition Tool name 'get_feed_items' indicates retrieval of feed data. Server context shows 'check_feeds' as a sibling tool, and the server description mentions 'live feeds' access. The tool name pattern follows standard read-operation conventions (get_*).
Documented attack patterns abuse exactly the kind of access get_feed_items gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Noapi Google Search, and nothing reaches the server without passing your rules. This is the rule we recommend for get_feed_items:
{
"version": "1",
"default": "deny",
"tools": {
"get_feed_items": {}
}
}get_feed_items is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_feed_items. It is categorised as a Read tool in the Noapi Google Search MCP Server, which means it retrieves data without modifying state.
Register the Noapi Google Search MCP server in PolicyLayer and add a rule for get_feed_items: 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 Noapi Google Search. Nothing to install.
get_feed_items 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 get_feed_items 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 get_feed_items. 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.
get_feed_items is provided by the Noapi Google Search MCP server (vincentkaufmann/noapi-google-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 38 Noapi Google Search tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
38 Noapi Google Search tools catalogued and risk-classified — across an index of 42,500+ MCP servers.