Search earthquakes by time range, magnitude, depth, location radius, PAGER alert level, or felt reports. Supports USGS (global, richer metadata: PAGER, DYFI, ShakeMap) and EMSC (European-Mediterranean, independent catalog). For location-based queries, provide latitude, longitude, and radius_km to...
Risk signalsHigh parameter count (15 properties)
Part of the Earthquake Mcp Server server.
Free to start. No card required.
AI agents call earthquake_search to retrieve information from Earthquake Mcp Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though earthquake_search only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"earthquake_search": {}
}
}See the full Earthquake Mcp Server policy for all 4 tools.
These attack patterns abuse exactly the kind of access earthquake_search gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Search earthquakes by time range, magnitude, depth, location radius, PAGER alert level, or felt reports. Supports USGS (global, richer metadata: PAGER, DYFI, ShakeMap) and EMSC (European-Mediterranean, independent catalog). For location-based queries, provide latitude, longitude, and radius_km together. USGS-specific filters (alert_level, min_felt, min_significance) are ignored when source=emsc. Use earthquake_count first to gauge result size before requesting large result sets. Results are capped at 20,000 events per query.. It is categorised as a Read tool in the Earthquake Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Earthquake Mcp Server MCP server in PolicyLayer and add a rule for earthquake_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 Earthquake Mcp Server. Nothing to install.
earthquake_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_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_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_search is provided by the Earthquake Mcp Server MCP server (@cyanheads/earthquake-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Earthquake Mcp Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.