earth.fires.detect
Active fire hotspots detected by NASA satellites (VIIRS, MODIS) — latitude, longitude, brightness, confidence, fire radiative power. Filter by bounding box and days. Near real-time updates (NASA FIRMS)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/earth.fires.detect.md
What earth.fires.detect does on Apibase
AI agents call earth.fires.detect 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 |
|---|---|---|---|
days | integer | — | Number of days of data (1-5, default 1) |
east | number | Yes | Eastern longitude of bounding box (e.g. -114) |
west | number | Yes | Western longitude of bounding box (e.g. -125 for California) |
north | number | Yes | Northern latitude of bounding box (e.g. 42) |
south | number | Yes | Southern latitude of bounding box (e.g. 32) |
source | string | — | Satellite sensor: VIIRS_SNPP_NRT (default, highest resolution), MODIS_NRT (legacy) |
Parameters from the server's own tool schema.
Why earth.fires.detect is rated Low
Tool queries real-time fire detection data without creating, modifying, or deleting information.
From the tool's definition retrieves active fire hotspots from NASA satellites; no side effects
Attacks that exploit this kind of access
The rule that runs earth.fires.detect 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 earth.fires.detect, this is the rule to start with:
earth.fires.detect 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 earth.fires.detect call is checked against it from then on.
Questions about earth.fires.detect
Active fire hotspots detected by NASA satellites (VIIRS, MODIS) — latitude, longitude, brightness, confidence, fire radiative power. Filter by bounding box and days. Near real-time updates (NASA FIRMS). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
earth.fires.detect accepts 6 parameters: days, east, west, north, south, source. Required: east, west, north, south. 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 earth.fires.detect: 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.
earth.fires.detect 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.fires.detect 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.fires.detect. 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.fires.detect 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