Get AMeDAS station information by station code.
AI agents call get_station_info 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 metadata about weather observation stations. It queries existing station data by identifier but does not create, modify, delete, or execute operations. The sibling tools (list_stations, search_nearby_stations) further confirm this is a data retrieval API for a read-only meteorological database.
From the tool's definition Tool name 'get_station_info' and description 'Get AMeDAS station information by station code' indicate a retrieval operation.
Attacks that exploit this kind of access
Get AMeDAS station information by station code. 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_station_info: 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_station_info 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_station_info 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_station_info. 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_station_info 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 →