earthquake_recent
Recent earthquakes from USGS. Filter by region (lat/lon + radius), state name, magnitude threshold, or time window.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/earthquake-recent.md
What earthquake_recent does on Livedatalink
AI agents call earthquake_recent 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 |
|---|---|---|---|
lat | number | — | |
lon | number | — | |
limit | number | — | Max events (default 50). |
end_time | string | — | ISO datetime upper bound (default now). |
location | string | — | Address, zip, city, or 'lat,lon' to center the search. Optional. |
radius_km | number | — | Search radius around lat/lon (max ~20000). |
start_time | string | — | ISO datetime lower bound (default 30 days ago). |
min_magnitude | number | — | Minimum magnitude (default 2.5). |
Parameters from the server's own tool schema.
Why earthquake_recent is rated Low
Even though earthquake_recent only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs earthquake_recent 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 earthquake_recent, this is the rule to start with:
earthquake_recent 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 earthquake_recent call is checked against it from then on.
Questions about earthquake_recent
Recent earthquakes from USGS. Filter by region (lat/lon + radius), state name, magnitude threshold, or time window. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
earthquake_recent accepts 8 parameters: lat, lon, limit, end_time, location, radius_km, start_time, 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 earthquake_recent: 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.
earthquake_recent 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_recent 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_recent. 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_recent 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