eonet.events.detail
Retrieve the full detail record for a specific NASA EONET natural disaster event by its EONET event ID (e.g. "EONET_20606"). Returns all geometry points (coordinates, magnitude, timestamps) for the entire event lifecycle, associated categories, and primary data source URLs. Useful for tracking th...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/eonet.events.detail.md
What eonet.events.detail does on Apibase
AI agents call eonet.events.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 |
|---|---|---|---|
id | string | Yes | EONET event ID (e.g. "EONET_20606"). Obtain from the eonet.events.list tool. |
Parameters from the server's own tool schema.
Why eonet.events.detail is rated Low
Tool retrieves and queries NASA disaster event data without modifying, deleting, or executing operations.
From the tool's definition Retrieve the full detail record for a specific NASA EONET natural disaster event by its EONET event ID
Attacks that exploit this kind of access
The rule that runs eonet.events.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 eonet.events.detail, this is the rule to start with:
eonet.events.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 eonet.events.detail call is checked against it from then on.
Questions about eonet.events.detail
Retrieve the full detail record for a specific NASA EONET natural disaster event by its EONET event ID (e.g. "EONET_20606"). Returns all geometry points (coordinates, magnitude, timestamps) for the entire event lifecycle, associated categories, and primary data source URLs. Useful for tracking the full track of a hurricane, the spread of a wildfire, or the progression of a flood. Obtain EONET IDs from the eonet.events.list tool. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
eonet.events.detail accepts 1 parameter: id. Required: id. 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 eonet.events.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.
eonet.events.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 eonet.events.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 eonet.events.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.
eonet.events.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