eonet.events.categories
List all available natural event categories in the NASA EONET system with their IDs, titles, and descriptions. Returns all 13 categories: drought, dustHaze, earthquakes, floods, landslides, manmade, seaLakeIce, severeStorms, snow, tempExtremes, volcanoes, waterColor, wildfires. Use category IDs a...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/eonet.events.categories.md
What eonet.events.categories does on Apibase
AI agents call eonet.events.categories 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 |
|---|---|---|---|
locale | string | — | Reserved for future use. Currently EONET returns English-only category names and descriptions. |
Parameters from the server's own tool schema.
Why eonet.events.categories is rated Low
Tool retrieves static reference data about event categories with no side effects or data modification.
From the tool's definition List all available natural event categories, returns IDs and descriptions
Attacks that exploit this kind of access
The rule that runs eonet.events.categories 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.categories, this is the rule to start with:
eonet.events.categories 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.categories call is checked against it from then on.
Questions about eonet.events.categories
List all available natural event categories in the NASA EONET system with their IDs, titles, and descriptions. Returns all 13 categories: drought, dustHaze, earthquakes, floods, landslides, manmade, seaLakeIce, severeStorms, snow, tempExtremes, volcanoes, waterColor, wildfires. Use category IDs as the "category" filter in eonet.events.list and as the "category_id" parameter in eonet.events.layers. No auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
eonet.events.categories accepts 1 parameter: locale. 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.categories: 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.categories 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.categories 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.categories. 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.categories 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