Get detailed weather information for a specified city as structured JSON data. This tool provides raw weather data for programmatic analysis and processing.
AI agents call get_weather_details 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 |
include_forecast | boolean | — | Whether to include forecast data (next 24 hours) |
Parameters from the server's own tool schema.
This tool performs a query operation that retrieves and returns weather data without creating, modifying, deleting, or executing any operations. The structured JSON response is informational only. Even if misused by an agent, it cannot cause harm—the blast radius is minimal as it only reads publicly available weather information.
From the tool's definition Tool name 'get_weather_details' and description 'Get detailed weather information for a specified city as structured JSON data' indicate data retrieval with no modification, deletion, or side effects.
Documented attack patterns abuse exactly the kind of access get_weather_details 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_weather_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_weather_details": {}
}
}get_weather_details 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 detailed weather information for a specified city as structured JSON data. This tool provides raw weather data for programmatic analysis and processing. It is categorised as a Read tool in the Weather MCP Server MCP Server, which means it retrieves data without modifying state.
get_weather_details accepts 2 parameters: city, include_forecast. 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_weather_details: 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_details 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_details 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_details. 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_details 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.