jma-bosai.reference.areas
Get the complete list of Japan Meteorological Agency (JMA) forecast area codes with Japanese and English names. Returns all 58 JMA offices/regions with 6-digit codes needed by jma-bosai.weather.forecast, jma-bosai.weather.overview, and jma-bosai.weather.warnings. Filter by English name keyword (e...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/jma-bosai.reference.areas.md
What jma-bosai.reference.areas does on Apibase
AI agents call jma-bosai.reference.areas 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 |
|---|---|---|---|
name_filter | string | — | Optional English keyword to filter offices by name (case-insensitive). E.g. "tokyo", "osaka". Leave empty to return all 58 offices. |
Parameters from the server's own tool schema.
Why jma-bosai.reference.areas is rated Low
Tool retrieves static reference data with no side effects, reversible operations, or external state changes.
From the tool's definition Get the complete list of Japan Meteorological Agency forecast area codes with Japanese and English names.
Attacks that exploit this kind of access
The rule that runs jma-bosai.reference.areas 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.reference.areas, this is the rule to start with:
jma-bosai.reference.areas 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.reference.areas call is checked against it from then on.
Questions about jma-bosai.reference.areas
Get the complete list of Japan Meteorological Agency (JMA) forecast area codes with Japanese and English names. Returns all 58 JMA offices/regions with 6-digit codes needed by jma-bosai.weather.forecast, jma-bosai.weather.overview, and jma-bosai.weather.warnings. Filter by English name keyword (e.g. "tokyo", "osaka") to find the right code. Example codes: 130000=Tokyo, 270000=Osaka, 230000=Aichi (Nagoya), 400000=Fukuoka. Data: JMA area constants — 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.reference.areas accepts 1 parameter: name_filter. 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.reference.areas: 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.reference.areas 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.reference.areas 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.reference.areas. 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.reference.areas 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