jma-bosai.weather.forecast
Get the official 3-day weather forecast from the Japan Meteorological Agency (JMA) for a specified area code (prefecture/region). Returns weather descriptions, wind conditions, wave heights, precipitation probability (%), and temperature (°C) per time period. Pass a 6-digit JMA area code (e.g. 13...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/jma-bosai.weather.forecast.md
What jma-bosai.weather.forecast does on Apibase
AI agents call jma-bosai.weather.forecast 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.forecast is rated Low
Retrieves weather forecast data with no side effects, modifications, or operational impact on systems or finances.
From the tool's definition Get the official 3-day weather forecast from the Japan Meteorological Agency (JMA)
Attacks that exploit this kind of access
The rule that runs jma-bosai.weather.forecast 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.forecast, this is the rule to start with:
jma-bosai.weather.forecast 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.forecast call is checked against it from then on.
Questions about jma-bosai.weather.forecast
Get the official 3-day weather forecast from the Japan Meteorological Agency (JMA) for a specified area code (prefecture/region). Returns weather descriptions, wind conditions, wave heights, precipitation probability (%), and temperature (°C) per time period. Pass a 6-digit JMA area code (e.g. 130000 for Tokyo, 270000 for Osaka). Use jma-bosai.reference.areas to look up valid area codes. Data: JMA official forecast — 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.forecast 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.forecast: 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.forecast 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.forecast 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.forecast. 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.forecast 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