AI agents call weather.zip to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves weather data from a public source (NOAA National Weather Service). It performs a read-only lookup based on a ZIP code parameter. No data is created, modified, deleted, or executed. The financial context of the MCP server (pay-per-call settlement) does not change the tool's operation; the pricing is infrastructure-level, not a financial action taken by the tool itself.
From the tool's definition Tool retrieves current US weather data for a ZIP code from NOAA NWS. Returns weather information without modifying data or triggering external operations. Query-only operation with no side effects.
Attacks that exploit this kind of access
Current US weather for a ZIP code (NOAA NWS). It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for weather.zip: 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. Nothing to install.
weather.zip 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 weather.zip 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 weather.zip. 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.
weather.zip is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →