earthquake.events.search
Search global earthquakes by time, location, magnitude, and depth — returns magnitude, coordinates, tsunami flags, PAGER alerts, and felt reports. 100+ years of data, updated every minute (USGS)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/earthquake.events.search.md
What earthquake.events.search does on Apibase
AI agents call earthquake.events.search 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 results (default 20, max 200) |
endtime | string | — | End date in ISO 8601 format (default: now) |
orderby | string | — | Sort order: "time" (newest first, default), "time-asc", "magnitude" (largest first), "magnitude-asc" |
latitude | number | — | Center latitude for radius search (-90 to 90) |
maxdepth | number | — | Maximum depth in kilometers (max 1000) |
mindepth | number | — | Minimum depth in kilometers (negative = above sea level) |
longitude | number | — | Center longitude for radius search (-180 to 180) |
starttime | string | — | Start date in ISO 8601 format, e.g. "2026-01-01" or "2026-01-01T00:00:00" |
alertlevel | string | — | PAGER alert level filter: green (no damage), yellow, orange, red (significant damage/casualties) |
maxradiuskm | number | — | Search radius in kilometers from lat/lon center point (max ~20,000 km) |
maxmagnitude | number | — | Maximum magnitude on Richter scale |
minmagnitude | number | — | Minimum magnitude on Richter scale (e.g. 4.5 for significant earthquakes) |
Parameters from the server's own tool schema.
Why earthquake.events.search is rated Low
Retrieves historical and real-time earthquake data with no side effects or operational impact.
From the tool's definition Search global earthquakes by time, location, magnitude... returns magnitude, coordinates, tsunami flags, PAGER alerts
Risk signalsHigh parameter count (12 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs earthquake.events.search 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 earthquake.events.search, this is the rule to start with:
earthquake.events.search 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 earthquake.events.search call is checked against it from then on.
Questions about earthquake.events.search
Search global earthquakes by time, location, magnitude, and depth — returns magnitude, coordinates, tsunami flags, PAGER alerts, and felt reports. 100+ years of data, updated every minute (USGS). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
earthquake.events.search accepts 12 parameters: limit, endtime, orderby, latitude, maxdepth, mindepth, longitude, starttime, alertlevel, maxradiuskm, maxmagnitude, minmagnitude. 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 earthquake.events.search: 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.
earthquake.events.search 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 earthquake.events.search 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 earthquake.events.search. 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.
earthquake.events.search 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