p2pquake.seismic.quake_history
Search historical JMA earthquake records via the P2PQuake history endpoint. Supports pagination, intensity and magnitude filters, and prefecture filtering for deeper analysis. Returns epicenter name, coordinates, depth, Richter magnitude, max JMA intensity label, domestic tsunami advisory, report...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/p2pquake.seismic.quake-history.md
What p2pquake.seismic.quake_history does on Apibase
AI agents call p2pquake.seismic.quake_history 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 | — | Number of historical earthquake records to return (default 20, max 100) |
order | integer | — | Sort direction: -1 for newest-first (default), 1 for oldest-first |
offset | integer | — | Pagination offset for browsing older events (0-based, default 0) |
max_scale | integer | — | Maximum JMA seismic intensity raw scale value |
min_scale | integer | — | Minimum JMA intensity (10=Shindo1, 20=Shindo2, 30=Shindo3, 40=Shindo4, 45=Shindo4+, 50=Shindo5w, 55=Shindo5s, 60=Shindo6w, 65=Shindo6s, 70=Shindo7) |
prefecture | integer | — | Filter by prefecture JIS code (1=Hokkaido, 13=Tokyo, 27=Osaka, 40=Fukuoka, 47=Okinawa) |
max_magnitude | number | — | Maximum Richter magnitude |
min_magnitude | number | — | Minimum Richter magnitude (e.g. 6.0 for strong earthquakes) |
Parameters from the server's own tool schema.
Why p2pquake.seismic.quake_history is rated Low
Tool queries and retrieves historical earthquake data with no side effects or ability to modify underlying information.
From the tool's definition Search historical JMA earthquake records via the P2PQuake history endpoint. Returns epicenter name, coordinates, depth, magnitude, intensity label.
Attacks that exploit this kind of access
The rule that runs p2pquake.seismic.quake_history 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 p2pquake.seismic.quake_history, this is the rule to start with:
p2pquake.seismic.quake_history 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 p2pquake.seismic.quake_history call is checked against it from then on.
Questions about p2pquake.seismic.quake_history
Search historical JMA earthquake records via the P2PQuake history endpoint. Supports pagination, intensity and magnitude filters, and prefecture filtering for deeper analysis. Returns epicenter name, coordinates, depth, Richter magnitude, max JMA intensity label, domestic tsunami advisory, report type, and observation point count. Use this for trend analysis, seismic risk assessment, or retrieving older events not in the recent feed. Filter examples: min_scale=60 for Shindo 6+ events, min_magnitude=7.0 for major quakes, prefecture=13 for Tokyo area events. Data source: P2PQuake — community-operated JMA relay, 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.
p2pquake.seismic.quake_history accepts 8 parameters: limit, order, offset, max_scale, min_scale, prefecture, max_magnitude, 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 p2pquake.seismic.quake_history: 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.
p2pquake.seismic.quake_history 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 p2pquake.seismic.quake_history 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 p2pquake.seismic.quake_history. 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.
p2pquake.seismic.quake_history 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