jpl.events.fireballs
Get reported fireball (bolide) events — atmospheric entry energy, velocity, altitude, geographic coordinates (NASA JPL CNEOS)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/jpl.events.fireballs.md
What jpl.events.fireballs does on Apibase
AI agents call jpl.events.fireballs 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 |
|---|---|---|---|
sort | string | — | Sort field (default: date descending) |
limit | integer | — | Maximum number of results (default 20, max 100) |
date_max | string | — | Maximum event date in YYYY-MM-DD format |
date_min | string | — | Minimum event date in YYYY-MM-DD format |
energy_min | number | — | Minimum radiated energy in Joules (e.g. 1e10) |
Parameters from the server's own tool schema.
Why jpl.events.fireballs is rated Low
Retrieves historical fireball event data from NASA JPL CNEOS; no creation, modification, or destructive capability.
From the tool's definition Get reported fireball events — atmospheric entry energy, velocity, altitude, coordinates
Attacks that exploit this kind of access
The rule that runs jpl.events.fireballs 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 jpl.events.fireballs, this is the rule to start with:
jpl.events.fireballs 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 jpl.events.fireballs call is checked against it from then on.
Questions about jpl.events.fireballs
Get reported fireball (bolide) events — atmospheric entry energy, velocity, altitude, geographic coordinates (NASA JPL CNEOS). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
jpl.events.fireballs accepts 5 parameters: sort, limit, date_max, date_min, energy_min. 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 jpl.events.fireballs: 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.
jpl.events.fireballs 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 jpl.events.fireballs 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 jpl.events.fireballs. 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.
jpl.events.fireballs 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