AI agents call google_weather 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.
Weather lookup is a read-only operation that retrieves data with no side effects, no state modification, and no irreversible actions. It fits the Read category. Severity is low because misuse would only leak or retrieve weather information, posing minimal risk. The confidence is 0.85 rather than higher because the description is empty; however, the tool name and sibling tool patterns provide sufficient evidence.
From the tool's definition Tool name 'google_weather' indicates retrieval of weather data. Server description emphasizes 'access to Google search, live feeds' and other query/retrieval operations.
Documented attack patterns abuse exactly the kind of access google_weather 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_weather:
{
"version": "1",
"default": "deny",
"tools": {
"google_weather": {}
}
}google_weather 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_weather. 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_weather: 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_weather 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_weather 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_weather. 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_weather 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.