AI agents call jpl_nhats 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 provides access to NASA's Near-Earth Object Hazard Assessment Tool data, which is fundamentally a query/retrieval interface for publicly available scientific data. There is no indication of write, delete, execution, or financial capabilities.
From the tool's definition Tool name 'jpl_nhats' and description 'Human-accessible NEOs (Near-Earth Objects) data' indicate data retrieval from NASA's JPL database.
Attacks that exploit this kind of access
Human-accessible NEOs (Near-Earth Objects) 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 jpl_nhats: 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.
jpl_nhats 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_nhats 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_nhats. 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_nhats 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 →