AI agents call nasa_firms to retrieve information from Nasa without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves fire information and data from NASA's FIRMS system. It has no capacity to modify, delete, or execute operations—it only queries and returns fire-related data. The passive framing ('fire data') and the nature of the FIRMS system as a public information resource for monitoring fires confirm this is a read-only tool with minimal security risk.
From the tool's definition Tool name 'nasa_firms' and description 'NASA Fire Information for Resource Management System - fire data' indicate data retrieval functionality. The description uses 'data' (passive noun), not action verbs like 'delete', 'execute', 'create', or 'modify'.
Attacks that exploit this kind of access
NASA Fire Information for Resource Management System - fire data. It is categorised as a Read tool in the Nasa MCP Server, which means it retrieves data without modifying state.
Register the Nasa MCP server in PolicyLayer and add a rule for nasa_firms: 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 Nasa. Nothing to install.
nasa_firms 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 nasa_firms 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 nasa_firms. 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.
nasa_firms is provided by the Nasa MCP server (@programcomputer/nasa-mcp-server). 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 →