Get current weather from the nearest AMeDAS station to given coordinates.
AI agents call get_weather_by_location 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.
This tool retrieves real-time weather observations from Japan Meteorological Agency stations based on geographic coordinates. It performs a query operation with no side effects—it does not modify, delete, or execute any external operations. The data returned is read-only observational weather information. This is a straightforward read operation with minimal security risk.
From the tool's definition Tool name 'get_weather_by_location' and description 'Get current weather from the nearest AMeDAS station' indicate retrieval of meteorological data with no modification, creation, deletion, or execution of commands.
Attacks that exploit this kind of access
Get current weather from the nearest AMeDAS station to given coordinates. 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_weather_by_location: 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_weather_by_location 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_by_location 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_by_location. 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_by_location 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 →