nasantrs.reports.stats
Get aggregate statistics for the entire NASA Technical Reports Server corpus. Returns total document count (645,000+) and breakdowns by: document type (conference paper, contractor report, technical memorandum, presentation, reprint, etc.), subject category (astrophysics, aerodynamics, geophysics...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nasantrs.reports.stats.md
What nasantrs.reports.stats does on Apibase
AI agents call nasantrs.reports.stats 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 |
|---|---|---|---|
detail | boolean | — | When true, returns full aggregation breakdowns by document type, subject category, NASA center, and top keywords. Always true — parameter reserved for future us |
Parameters from the server's own tool schema.
Why nasantrs.reports.stats is rated Low
Tool retrieves and aggregates pre-computed statistics from corpus with no side effects or modifications.
From the tool's definition Get aggregate statistics, document count, breakdowns, research keywords
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs nasantrs.reports.stats 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.stats, this is the rule to start with:
nasantrs.reports.stats 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.stats call is checked against it from then on.
Questions about nasantrs.reports.stats
Get aggregate statistics for the entire NASA Technical Reports Server corpus. Returns total document count (645,000+) and breakdowns by: document type (conference paper, contractor report, technical memorandum, presentation, reprint, etc.), subject category (astrophysics, aerodynamics, geophysics, propulsion, etc.), and NASA center (JPL, GSFC, LaRC, MSFC, ARC, JSC, etc.). Also returns the top research keywords across the corpus. Useful for understanding the scope and distribution of NASA's documented research output. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nasantrs.reports.stats accepts 1 parameter: detail. 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.stats: 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.stats 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.stats 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.stats. 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.stats 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