AI agents call resolve_links to retrieve information from Nasa Ads without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/resolves links associated with a bibcode, such as arXiv links, PDFs, DOIs, and data products. It is purely a read/fetch operation with no side effects, modifications, or destructive actions.
From the tool's definition Resolver links for a bibcode (arxiv, PDF, DOI, data products, etc.)
Attacks that exploit this kind of access
Resolver links for a bibcode (arxiv, PDF, DOI, data products, etc.). It is categorised as a Read tool in the Nasa Ads MCP Server, which means it retrieves data without modifying state.
Register the Nasa Ads MCP server in PolicyLayer and add a rule for resolve_links: 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 Ads. Nothing to install.
resolve_links 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 resolve_links 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 resolve_links. 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.
resolve_links is provided by the Nasa Ads MCP server (mubashir1osmani/nasa-ads). 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 →