earthquake.events.count
Count earthquakes matching search criteria without returning full data — useful for statistics and monitoring thresholds (USGS)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/earthquake.events.count.md
What earthquake.events.count does on Apibase
AI agents call earthquake.events.count 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 |
|---|---|---|---|
endtime | string | — | End date in ISO 8601 format (default: now) |
latitude | number | — | Center latitude for radius search |
longitude | number | — | Center longitude for radius search |
starttime | string | — | Start date in ISO 8601 format, e.g. "2026-01-01" |
maxradiuskm | number | — | Search radius in kilometers from lat/lon center |
maxmagnitude | number | — | Maximum magnitude on Richter scale |
minmagnitude | number | — | Minimum magnitude on Richter scale |
Parameters from the server's own tool schema.
Why earthquake.events.count is rated Low
Retrieves earthquake statistics via query without side effects or data modification.
From the tool's definition Count earthquakes matching search criteria without returning full data
Attacks that exploit this kind of access
The rule that runs earthquake.events.count 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.count, this is the rule to start with:
earthquake.events.count 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.count call is checked against it from then on.
Questions about earthquake.events.count
Count earthquakes matching search criteria without returning full data — useful for statistics and monitoring thresholds (USGS). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
earthquake.events.count accepts 7 parameters: endtime, latitude, longitude, starttime, 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.count: 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.count 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.count 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.count. 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.count 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