nasaexoplanet.planets.stats
Get discovery statistics for confirmed exoplanets aggregated by method, year, or facility. Group by "method" to see Transit vs Radial Velocity vs Imaging counts, "year" for annual discovery trends since 1988, or "facility" to rank observatories and missions (Kepler, TESS, Keck, etc.) by total dis...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nasaexoplanet.planets.stats.md
What nasaexoplanet.planets.stats does on Apibase
AI agents call nasaexoplanet.planets.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 |
|---|---|---|---|
limit | integer | — | Maximum number of groups to return (default 50, max 100) |
group_by | string | — | Dimension to aggregate by: "method" (discovery method counts), "year" (annual discoveries), or "facility" (telescope/observatory counts). Default: method |
Parameters from the server's own tool schema.
Why nasaexoplanet.planets.stats is rated Low
Retrieves and aggregates public NASA exoplanet discovery statistics without side effects or data modification.
From the tool's definition Get discovery statistics for confirmed exoplanets aggregated by method, year, or facility.
Attacks that exploit this kind of access
The rule that runs nasaexoplanet.planets.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 nasaexoplanet.planets.stats, this is the rule to start with:
nasaexoplanet.planets.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 nasaexoplanet.planets.stats call is checked against it from then on.
Questions about nasaexoplanet.planets.stats
Get discovery statistics for confirmed exoplanets aggregated by method, year, or facility. Group by "method" to see Transit vs Radial Velocity vs Imaging counts, "year" for annual discovery trends since 1988, or "facility" to rank observatories and missions (Kepler, TESS, Keck, etc.) by total discoveries (NASA Exoplanet Archive). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nasaexoplanet.planets.stats accepts 2 parameters: limit, group_by. 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 nasaexoplanet.planets.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.
nasaexoplanet.planets.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 nasaexoplanet.planets.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 nasaexoplanet.planets.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.
nasaexoplanet.planets.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