usgs_earthquake_detail
Get full detail for a specific earthquake event by USGS event ID. Returns origin, magnitude details, focal mechanism (if available), shake-map link, felt reports, tsunami flag, and impact estimates.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/usgs-earthquake-detail.md
What usgs_earthquake_detail does on Livedatalink
AI agents call usgs_earthquake_detail 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 |
|---|---|---|---|
event_id | string | Yes | USGS event ID (e.g. 'us7000m5dt'). Get from feed or search results. |
Parameters from the server's own tool schema.
Why usgs_earthquake_detail is rated Low
This tool retrieves historical earthquake information from USGS databases. It is purely informational—querying an event ID to return details like magnitude, origin, shake-maps, and impact estimates. There is no capability to modify data, execute commands, delete records, or incur financial obligations.
From the tool's definition Tool name 'usgs_earthquake_detail' and description 'Get full detail for a specific earthquake event' indicate data retrieval.
Attacks that exploit this kind of access
The rule that runs usgs_earthquake_detail 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_detail, this is the rule to start with:
usgs_earthquake_detail 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_detail call is checked against it from then on.
Questions about usgs_earthquake_detail
Get full detail for a specific earthquake event by USGS event ID. Returns origin, magnitude details, focal mechanism (if available), shake-map link, felt reports, tsunami flag, and impact estimates. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
usgs_earthquake_detail accepts 1 parameter: event_id. Required: event_id. 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_detail: 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_detail 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_detail 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_detail. 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_detail 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