get_historical_weather
AI agents call get_historical_weather to retrieve information from JMA Data MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves historical weather information from the JMA database. This is a read-only operation with no side effects—it queries existing data without modifying, deleting, or executing external operations. The naming convention aligns with other benign read operations on this weather data server. Confidence is slightly reduced due to empty description, but context makes the classification clear.
From the tool's definition Tool name 'get_historical_weather' indicates retrieval of past weather data. No description provided, but context from sibling tools (all read-only queries: get_current_weather, get_forecast, get_station_info, list_*, search_*) and server purpose (provides…
Attacks that exploit this kind of access
get_historical_weather. It is categorised as a Read tool in the JMA Data MCP MCP Server, which means it retrieves data without modifying state.
Register the JMA Data MCP server in PolicyLayer and add a rule for get_historical_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 JMA Data MCP. Nothing to install.
get_historical_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_historical_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_historical_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_historical_weather is provided by the JMA Data MCP server (koizumikento/jma-data-mcp). 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 →