crawl_context_product
AI agents call crawl_context_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.
The tool appears to navigate or crawl context related to a product within a public astronomical data registry. While the description is empty, the naming pattern ('crawl_context_product') suggests traversal/retrieval of data structures rather than mutations, destructive actions, or code execution. The sibling tools are all search/retrieval operations.
From the tool's definition Tool name 'crawl_context_product' and sibling tools ('get_product', 'search_*') indicate data retrieval operations from the NASA PDS Registry API.
Attacks that exploit this kind of access
crawl_context_product. 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 crawl_context_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.
crawl_context_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 crawl_context_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 crawl_context_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.
crawl_context_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 →