search_collections
AI agents call search_collections 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 searches a registry or catalog of collections within the NASA Planetary Data System. Search operations are inherently read-only queries that retrieve information without side effects, creating, modifying, or deleting data. The low severity reflects minimal blast radius if misused—returning unwanted search results causes no damage.
From the tool's definition Tool name 'search_collections' indicates a search operation. The server description emphasizes 'search and exploration' of planetary data products.
Attacks that exploit this kind of access
search_collections. 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_collections: 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_collections 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_collections 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_collections. 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_collections 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 →