This record as markdown: /tools/firebase-genkit/weathertool.md
What weatherTool does on Genkit MCP
AI agents call weatherTool to retrieve information from Genkit MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why weatherTool is rated Low
This tool retrieves weather information for display purposes. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions or destructive operations. It is a straightforward read operation that fetches data from a weather service and presents it to the user.
From the tool's definition Tool name 'weatherTool' with description 'use this tool to display weather' indicates a query operation that retrieves and presents weather data without modifying, executing operations, or affecting external systems.
Attacks that exploit this kind of access
The rule that runs weatherTool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genkit MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For weatherTool, this is the rule to start with:
weatherTool is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Genkit MCP, apply this rule, and every weatherTool call is checked against it from then on.
Questions about weatherTool
use this tool to display weather. It is categorised as a Read tool in the Genkit MCP MCP Server, which means it retrieves data without modifying state.
Register the Genkit MCP server in PolicyLayer and add a rule for weatherTool: 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 Genkit MCP. Nothing to install.
weatherTool 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 weatherTool 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 weatherTool. 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.
weatherTool is provided by the Genkit MCP server (genkit-ai/genkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genkit, and thousands of servers like it.
This server
Across the catalogue