jma-bosai.seismic.recent
Get the most recent earthquakes reported by the Japan Meteorological Agency (JMA). Returns epicenter name (English and Japanese), magnitude, JMA seismic intensity (Shindo scale 1–7), coordinates, depth (km), and occurrence time in ISO 8601. Filter by minimum magnitude to focus on significant even...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/jma-bosai.seismic.recent.md
What jma-bosai.seismic.recent does on Apibase
AI agents call jma-bosai.seismic.recent 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 |
|---|---|---|---|
limit | integer | — | Maximum number of earthquakes to return (1–100). Defaults to 20. |
min_magnitude | number | — | Filter — return only earthquakes with magnitude ≥ this value (e.g. 3.0). |
Parameters from the server's own tool schema.
Why jma-bosai.seismic.recent is rated Low
Retrieves read-only earthquake data from a public government feed with no side effects.
From the tool's definition Get the most recent earthquakes reported by JMA
Attacks that exploit this kind of access
The rule that runs jma-bosai.seismic.recent 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.seismic.recent, this is the rule to start with:
jma-bosai.seismic.recent 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.seismic.recent call is checked against it from then on.
Questions about jma-bosai.seismic.recent
Get the most recent earthquakes reported by the Japan Meteorological Agency (JMA). Returns epicenter name (English and Japanese), magnitude, JMA seismic intensity (Shindo scale 1–7), coordinates, depth (km), and occurrence time in ISO 8601. Filter by minimum magnitude to focus on significant events. JMA Shindo scale: 1=barely felt, 4=hanging objects swing strongly, 5+=damage possible, 7=catastrophic. Complements p2pquake.seismic.recent (community network) with the official government feed. Data: JMA official seismic data — 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.seismic.recent accepts 2 parameters: limit, min_magnitude. 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.seismic.recent: 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.seismic.recent 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.seismic.recent 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.seismic.recent. 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.seismic.recent 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