Get Mars rover mission manifest and details.
AI agents call get_rover_manifest 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 static mission information (manifest and details) about Mars rovers. It performs no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions. The 'get' verb and 'manifest and details' object confirm this is a simple Read operation querying publicly available NASA data.
From the tool's definition Tool name 'get_rover_manifest' and description 'Get Mars rover mission manifest and details' indicate a retrieval operation that queries mission metadata from NASA's public APIs without modifying, executing, or deleting data.
Documented attack patterns abuse exactly the kind of access get_rover_manifest gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nasa, and nothing reaches the server without passing your rules. This is the rule we recommend for get_rover_manifest:
{
"version": "1",
"default": "deny",
"tools": {
"get_rover_manifest": {}
}
}get_rover_manifest is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get Mars rover mission manifest and details. 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 get_rover_manifest: 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.
get_rover_manifest 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 get_rover_manifest 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 get_rover_manifest. 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.
get_rover_manifest is provided by the Nasa MCP server (jezweb/nasa-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nasa, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Nasa tools catalogued and risk-classified — across an index of 43,000+ MCP servers.