AI agents call google_trends 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.
Google Trends retrieves historical and current search trend data. This is a read-only query operation with no side effects—it neither modifies data, executes code, deletes information, nor commits financial obligations. The blank description lowers confidence slightly, but the context of a search/feed aggregation server and naming convention strongly indicate a data retrieval function.
From the tool's definition Tool name 'google_trends' and server description indicating 'access to Google search, live feeds' suggests querying trend data.
Documented attack patterns abuse exactly the kind of access google_trends 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 google_trends:
{
"version": "1",
"default": "deny",
"tools": {
"google_trends": {}
}
}google_trends 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.
google_trends. 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 google_trends: 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.
google_trends 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 google_trends 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 google_trends. 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.
google_trends 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.