nasantrs.reports.detail
Get the full citation and metadata for a specific NASA technical report by its numeric NTRS ID. Returns complete record: title, full abstract, all authors with organizational affiliations, document type, NASA center, publication and submission dates, subject categories, keywords, report numbers, ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nasantrs.reports.detail.md
What nasantrs.reports.detail does on Apibase
AI agents call nasantrs.reports.detail to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
report_id | integer | Yes | Numeric NTRS submission/citation ID (e.g. 20140017767). Obtain from nasantrs.reports.search or nasantrs.reports.recent results. |
Parameters from the server's own tool schema.
Why nasantrs.reports.detail is rated Low
Retrieves and returns publicly accessible NASA technical report metadata and download URLs with no side effects.
From the tool's definition Get the full citation and metadata for a specific NASA technical report. Returns complete record.
Attacks that exploit this kind of access
The rule that runs nasantrs.reports.detail safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nasantrs.reports.detail, this is the rule to start with:
nasantrs.reports.detail is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every nasantrs.reports.detail call is checked against it from then on.
Questions about nasantrs.reports.detail
Get the full citation and metadata for a specific NASA technical report by its numeric NTRS ID. Returns complete record: title, full abstract, all authors with organizational affiliations, document type, NASA center, publication and submission dates, subject categories, keywords, report numbers, and direct PDF/fulltext download URLs. Use nasantrs.reports.search or nasantrs.reports.recent to find NTRS IDs, or extract the ID from the URL at ntrs.nasa.gov/citations/{id}. PDF download links point directly to the NASA server — freely accessible without authentication. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nasantrs.reports.detail accepts 1 parameter: report_id. Required: report_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for nasantrs.reports.detail: 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 Apibase. Nothing to install.
nasantrs.reports.detail 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 nasantrs.reports.detail 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 nasantrs.reports.detail. 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.
nasantrs.reports.detail is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue