AI agents call get_weather to retrieve information from MCP Weather Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns weather data without creating, modifying, deleting, or executing any operations. It has no destructive, financial, or code execution capabilities. The blast radius of misuse is minimal—an attacker could retrieve weather data for any location, but this causes no harm to systems or data integrity.
From the tool's definition Tool name 'get_weather' and description 'Get current weather information for a location' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_weather gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Weather Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_weather:
{
"version": "1",
"default": "deny",
"tools": {
"get_weather": {}
}
}get_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.
Get current weather information for a location. It is categorised as a Read tool in the MCP Weather Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Weather Server MCP server in PolicyLayer and add a rule for get_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 MCP Weather Server. Nothing to install.
get_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 get_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 get_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.
get_weather is provided by the MCP Weather Server MCP server (tjarriault/mcp-weather-sample). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Weather Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 MCP Weather Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.