nasa_firms_search_fires

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Low RISK CLASS

Category Read

Parameters 114 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/nasa-firms-search-fires.md

WHAT IT DOES

What nasa_firms_search_fires does on Livedatalink

AI agents call nasa_firms_search_fires to retrieve information from Livedatalink 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
`east`	number	Yes	Eastern longitude; must be greater than west.
`west`	number	Yes	Western longitude of the bounding box.
`limit`	integer	—	Maximum detections returned. Default 25.
`north`	number	Yes	Northern latitude; must be greater than south.
`south`	number	Yes	Southern latitude of the bounding box.
`offset`	integer	—	Rows to skip for pagination. Default 0.
`source`	string	—	NASA FIRMS sensor product. Default VIIRS_NOAA20_NRT.
`data_mode`	string	—	auto uses the D1 mirror when configured; hosted requires D1; live requires NASA_FIRMS_MAP_KEY. Default auto.
`day_range`	integer	—	Number of days from start_date, or most recent days when omitted. Default 1.
`start_date`	string	—	Optional first UTC date in YYYY-MM-DD form.
`response_format`	string	—	Human-readable markdown or machine-readable JSON. Default markdown.

Parameters from the server's own tool schema.

RISK

Why nasa_firms_search_fires is rated Low

Even though nasa_firms_search_fires only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsHigh parameter count (11 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs nasa_firms_search_fires safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nasa_firms_search_fires, this is the rule to start with:

nasa_firms_search_fires Allowed

nasa_firms_search_fires is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "nasa_firms_search_fires": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every nasa_firms_search_fires call is checked against it from then on.

FAQ

Questions about nasa_firms_search_fires

What does the nasa_firms_search_fires tool do? +

Search NASA FIRMS satellite active-fire/hotspot detections inside a bounded latitude/longitude box. Uses LiveDataLink's D1 mirror by default when configured, or the NASA Area API when live mode is requested. Results include acquisition time, satellite/sensor, confidence, fire radiative power, brightness, and day/night flag. Supports limit/offset pagination. A hotspot is a satellite thermal anomaly, not confirmation of a wildfire; verify consequential decisions with incident authorities and NASA FIRMS. The interactive bounding box is limited to 60 degrees wide by 30 degrees high; split larger regions into multiple calls. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does nasa_firms_search_fires accept? +

nasa_firms_search_fires accepts 11 parameters: east, west, limit, north, south, offset, source, data_mode, day_range, start_date, response_format. Required: east, west, north, south. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on nasa_firms_search_fires? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for nasa_firms_search_fires: 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 Livedatalink. Nothing to install.

What risk level is nasa_firms_search_fires? +

nasa_firms_search_fires is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit nasa_firms_search_fires? +

Yes. Add a rate_limit block to the nasa_firms_search_fires 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.

How do I block nasa_firms_search_fires completely? +

Set action: deny in the PolicyLayer policy for nasa_firms_search_fires. 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.

What MCP server provides nasa_firms_search_fires? +

nasa_firms_search_fires is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 381 Livedatalink tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →