Get weather information for a city, return json format for AI
AI agents call get_weather to retrieve information from Weather MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves weather data without creating, modifying, deleting, or executing operations. It is a straightforward read operation with no capability to alter state or cause harm. Severity is low because misuse cannot impact system integrity, data security, or financial obligations.
From the tool's definition Tool description states 'Get weather information for a city, return json format for AI' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get weather information for a city, return json format for AI. It is categorised as a Read tool in the Weather MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Weather MCP 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 Weather MCP 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 Weather MCP Server MCP server (theshypika/mcp-servers). 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 →