search_targets
AI agents call search_targets 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 performs a search query against the NASA PDS Registry API to retrieve celestial body or observation target information. It returns data without modifying, executing external operations, or causing destructive effects. The naming convention and context within a public registry access tool strongly indicate a read-only retrieval function.
From the tool's definition Tool name 'search_targets' combined with sibling tools (search_collections, search_instrument_hosts, search_instruments, search_investigations) all following search/retrieval patterns on a Registry API for querying planetary data products.
Attacks that exploit this kind of access
search_targets. 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 search_targets: 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.
search_targets 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 search_targets 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 search_targets. 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.
search_targets 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 →