AI agents call get_current_weather to retrieve information from Weather MCP Tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries weather data without side effects. It retrieves information from an external API and returns it to the user—a typical read operation. There is no capability to modify, delete, execute code, or trigger financial transactions. The low severity reflects minimal blast radius: incorrect weather data has negligible security or operational impact.
From the tool's definition Tool name 'get_current_weather' indicates a retrieval operation. Server description confirms the tool retrieves 'real-time weather data' and 'current conditions' from OpenWeatherMap API.
Documented attack patterns abuse exactly the kind of access get_current_weather gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Weather MCP Tool, and nothing reaches the server without passing your rules. This is the rule we recommend for get_current_weather:
{
"version": "1",
"default": "deny",
"tools": {
"get_current_weather": {}
}
}get_current_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. It is categorised as a Read tool in the Weather MCP Tool MCP Server, which means it retrieves data without modifying state.
Register the Weather MCP Tool 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 Weather MCP Tool. 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 Weather MCP Tool MCP server (saintdoresh/weather-mcp-claudedesktop). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Weather MCP Tool, 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 Weather MCP Tool tools catalogued and risk-classified — across an index of 43,000+ MCP servers.