emsc.seismic.event_detail
Get full detail for a single earthquake event from the EMSC real-time seismicity catalog by its event ID (unid), as returned by emsc.search_earthquakes. Optionally include all reported magnitude estimates and origin solutions, not just the preferred ones. Data: seismicportal.eu (EMSC), no auth re...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/emsc.seismic.event-detail.md
What emsc.seismic.event_detail does on Apibase
AI agents call emsc.seismic.event_detail 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 |
|---|---|---|---|
eventid | string | Yes | EMSC event unique ID / unid (e.g. 20260827_0000123), as returned by emsc.search_earthquakes. |
includeallorigins | boolean | — | Include all reported origin solutions for the event, not just the preferred one (default false). |
includeallmagnitudes | boolean | — | Include all reported magnitude estimates for the event, not just the preferred one (default false). |
Parameters from the server's own tool schema.
Why emsc.seismic.event_detail is rated Low
Retrieves earthquake event data from a public catalog with no side effects or mutations.
From the tool's definition Get full detail for a single earthquake event from the EMSC real-time seismicity catalog
Attacks that exploit this kind of access
The rule that runs emsc.seismic.event_detail 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 emsc.seismic.event_detail, this is the rule to start with:
emsc.seismic.event_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 Apibase, apply this rule, and every emsc.seismic.event_detail call is checked against it from then on.
Questions about emsc.seismic.event_detail
Get full detail for a single earthquake event from the EMSC real-time seismicity catalog by its event ID (unid), as returned by emsc.search_earthquakes. Optionally include all reported magnitude estimates and origin solutions, not just the preferred ones. Data: seismicportal.eu (EMSC), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
emsc.seismic.event_detail accepts 3 parameters: eventid, includeallorigins, includeallmagnitudes. Required: eventid. 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 emsc.seismic.event_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 Apibase. Nothing to install.
emsc.seismic.event_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 emsc.seismic.event_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 emsc.seismic.event_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.
emsc.seismic.event_detail 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