usgs_earthquake_search
Custom earthquake search via USGS fdsnws. Filter by magnitude, time range, and lat/lon bounding box. Returns up to 100 events sorted by time. Use this for analytical queries instead of the feed when you need historical or geographic filtering.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/usgs-earthquake-search.md
What usgs_earthquake_search does on Livedatalink
AI agents call usgs_earthquake_search to retrieve information from Livedatalink 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 | number | — | Max results (default 25, max 100) |
end_time | string | — | ISO date or full datetime |
start_time | string | — | ISO date or full datetime YYYY-MM-DD[THH:MM:SS] |
max_latitude | number | — | Bounding box north |
min_latitude | number | — | Bounding box south |
max_longitude | number | — | Bounding box east |
min_longitude | number | — | Bounding box west |
min_magnitude | number | — | Minimum magnitude (e.g. 4.5) |
Parameters from the server's own tool schema.
Why usgs_earthquake_search is rated Low
This tool queries the USGS earthquake database with optional filters and returns historical earthquake data. It is a read-only operation with no side effects—it retrieves and presents information without modifying any data or triggering external operations. The low severity reflects minimal risk to an AI agent using it; misuse would only result in retrieving unwanted earthquake data, not causing damage.
From the tool's definition Tool description states it performs a 'Custom earthquake search' and 'Returns up to 100 events sorted by time' with filtering capabilities. The verbs 'search' and 'filter' and 'returns' indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs usgs_earthquake_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For usgs_earthquake_search, this is the rule to start with:
usgs_earthquake_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 Livedatalink, apply this rule, and every usgs_earthquake_search call is checked against it from then on.
Questions about usgs_earthquake_search
Custom earthquake search via USGS fdsnws. Filter by magnitude, time range, and lat/lon bounding box. Returns up to 100 events sorted by time. Use this for analytical queries instead of the feed when you need historical or geographic filtering. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
usgs_earthquake_search accepts 8 parameters: limit, end_time, start_time, max_latitude, min_latitude, max_longitude, min_longitude, min_magnitude. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for usgs_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 Livedatalink. Nothing to install.
usgs_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 usgs_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 usgs_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.
usgs_earthquake_search is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue