Get current weather information for a specified city. It extracts the current hour's temperature and weather code, maps the weather code to a human-readable description, and returns a formatted summary.
AI agents call get_current_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
city | string | — | The name of the city to fetch weather information for, PLEASE NOTE English name only, if the parameter city isn't English please translate to English before inv |
Parameters from the server's own tool schema.
This tool retrieves and queries weather data with no side effects. It is a straightforward Read operation that fetches real-time information for display. The severity is low because weather data is public, non-sensitive, and retrieving it poses minimal security risk to the user's systems or data.
From the tool's definition Tool description explicitly states it 'Get current weather information' and 'extracts' data without modifying anything. The Open-Meteo API is a public weather data service that returns read-only information.
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 Server, 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 information for a specified city. It extracts the current hour's temperature and weather code, maps the weather code to a human-readable description, and returns a formatted summary. It is categorised as a Read tool in the Weather MCP Server MCP Server, which means it retrieves data without modifying state.
get_current_weather accepts 1 parameter: city. The full parameter table on this page comes from the server's own tool schema.
Register the Weather 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 Weather 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 Weather MCP Server MCP server (isdaniel/mcp_weather_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Weather MCP 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.
8 Weather MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.