get_current_weather
AI agents call get_current_weather to retrieve information from 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 current weather data from the OpenWeather API. No modification, deletion, or execution of external operations occurs—it simply fetches and returns information. The 'get_' prefix is a strong indicator of read-only behavior. Even with an empty description, the context of a weather API server and naming consistency support classification as Read with low severity.
From the tool's definition Tool name 'get_current_weather' indicates data retrieval with no side effects. Description is empty, but the naming convention and sibling tools (get_weather_alerts, get_weather_forecast, get_historical_weather) all follow a 'get_*' pattern typical of…
Attacks that exploit this kind of access
get_current_weather. It is categorised as a Read tool in the MCP-server MCP Server, which means it retrieves data without modifying state.
Register the MCP-server MCP server in PolicyLayer and add a rule for get_current_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-server. Nothing to install.
get_current_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_current_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_current_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_current_weather is provided by the MCP-server MCP server (prathapmahi/mcp-server). 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 →