Get a single PDS product by its URN identifier.
AI agents call get_product to retrieve information from NASA PDS Registry MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a specific planetary data product from the NASA Planetary Data System Registry by its unique identifier (URN). It performs no modifications, deletions, code execution, or financial operations. The operation is purely informational with no harmful side effects even if misused by an AI agent—at worst, it returns data the agent is already authorized to access.
From the tool's definition Tool name 'get_product' and description 'Get a single PDS product by its URN identifier' indicates a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get a single PDS product by its URN identifier. It is categorised as a Read tool in the NASA PDS Registry MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NASA PDS Registry MCP Server MCP server in PolicyLayer and add a rule for get_product: 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 PDS Registry MCP Server. Nothing to install.
get_product 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_product 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_product. 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_product is provided by the NASA PDS Registry MCP Server MCP server (nasa-pds/pds-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 →