Active and historical global natural events via NASA EONET v3: wildfires, severe storms, volcanoes, floods, droughts, landslides, sea/lake ice, dust/haze, manmade incidents, water-color anomalies. Each event includes geo-located observation points and category. Filter by status, days-back, catego...
AI agents call earth.events to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns information about natural events from NASA EONET (Earth Observation Natural Event Tracking). It has no capability to modify data, execute operations, delete records, or move money. The filtering parameters (status, days-back, category, bbox) are all read-only query constraints. Risk is minimal—misuse would only expose publicly available geolocation and event data.
From the tool's definition Tool retrieves 'active and historical global natural events' with filtering capabilities. Verbs used: 'includes', 'filter by' indicate data retrieval with no modification, creation, deletion, or execution of external operations.
Attacks that exploit this kind of access
Active and historical global natural events via NASA EONET v3: wildfires, severe storms, volcanoes, floods, droughts, landslides, sea/lake ice, dust/haze, manmade incidents, water-color anomalies. Each event includes geo-located observation points and category. Filter by status, days-back, category, or bbox. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for earth.events: 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 Mcp. Nothing to install.
earth.events 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 earth.events 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 earth.events. 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.
earth.events is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →