jma-bosai.weather.warnings
Get all currently active weather warnings and advisories issued by the Japan Meteorological Agency (JMA) for a specified area. Returns warning codes, statuses (issued / continuing / lifted), and a headline summary. Warning code meanings: 02=Wind, 03=Wave, 04=Thunderstorm, 05=Heavy Rain, 06=Windst...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/jma-bosai.weather.warnings.md
What jma-bosai.weather.warnings does on Apibase
AI agents call jma-bosai.weather.warnings to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
area_code | string | — | JMA 6-digit area (office) code. Use jma-bosai.reference.areas to look up valid codes. Common codes: 130000 (Tokyo), 270000 (Osaka), 230000 (Aichi/Nagoya), 40000 |
Parameters from the server's own tool schema.
Why jma-bosai.weather.warnings is rated Low
Tool retrieves read-only weather alert data from a public API with no side effects or modifications.
From the tool's definition Get all currently active weather warnings and advisories
Attacks that exploit this kind of access
The rule that runs jma-bosai.weather.warnings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jma-bosai.weather.warnings, this is the rule to start with:
jma-bosai.weather.warnings is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every jma-bosai.weather.warnings call is checked against it from then on.
Questions about jma-bosai.weather.warnings
Get all currently active weather warnings and advisories issued by the Japan Meteorological Agency (JMA) for a specified area. Returns warning codes, statuses (issued / continuing / lifted), and a headline summary. Warning code meanings: 02=Wind, 03=Wave, 04=Thunderstorm, 05=Heavy Rain, 06=Windstorm, 10=Tsunami, 12=Snow, 14=Avalanche, 15=Flood, 20=High Wave, etc. Pass a 6-digit JMA area code (e.g. 130000 for Tokyo). Data: JMA official warnings — Japanese Government open data, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
jma-bosai.weather.warnings accepts 1 parameter: area_code. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for jma-bosai.weather.warnings: 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 Apibase. Nothing to install.
jma-bosai.weather.warnings 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 jma-bosai.weather.warnings 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 jma-bosai.weather.warnings. 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.
jma-bosai.weather.warnings is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue