New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

nasaexoplanet.planets.habitable

Find potentially habitable exoplanets in the conservative habitable zone — planets with Earth-like radius (0.5–2.0 R⊕) and equilibrium temperature suitable for liquid water (180–310 K). Sorted by radius ascending. Returns radius, mass, orbital period, equilibrium temperature, insolation flux, and...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 50 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nasaexoplanet.planets.habitable.md

What nasaexoplanet.planets.habitable does on Apibase

AI agents call nasaexoplanet.planets.habitable 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.

ParameterTypeRequiredDescription
limit integer — Maximum number of candidates to return (default 20, max 100)
temp_max number — Maximum equilibrium temperature in Kelvin (default 310 — conservative habitable zone upper bound)
temp_min number — Minimum equilibrium temperature in Kelvin (default 180 — conservative habitable zone lower bound)
radius_max number — Maximum planet radius in Earth radii (default 2.0 — upper limit for rocky planets)
radius_min number — Minimum planet radius in Earth radii (default 0.5 — filters sub-Earth bodies)

Parameters from the server's own tool schema.

Why nasaexoplanet.planets.habitable is rated Low

Tool retrieves NASA exoplanet data with no side effects, modifications, or external operations.

From the tool's definition Find potentially habitable exoplanets, returns radius, mass, orbital period, temperature.

Questions about nasaexoplanet.planets.habitable

What does the nasaexoplanet.planets.habitable tool do? +

Find potentially habitable exoplanets in the conservative habitable zone — planets with Earth-like radius (0.5–2.0 R⊕) and equilibrium temperature suitable for liquid water (180–310 K). Sorted by radius ascending. Returns radius, mass, orbital period, equilibrium temperature, insolation flux, and host star details. Customisable temperature and radius bounds for optimistic or strict filtering (NASA Exoplanet Archive — pscomppars table). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does nasaexoplanet.planets.habitable accept? +

nasaexoplanet.planets.habitable accepts 5 parameters: limit, temp_max, temp_min, radius_max, radius_min. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on nasaexoplanet.planets.habitable? +

Register the Apibase MCP server in PolicyLayer and add a rule for nasaexoplanet.planets.habitable: 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.

What risk level is nasaexoplanet.planets.habitable? +

nasaexoplanet.planets.habitable is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit nasaexoplanet.planets.habitable? +

Yes. Add a rate_limit block to the nasaexoplanet.planets.habitable 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.

How do I block nasaexoplanet.planets.habitable completely? +

Set action: deny in the PolicyLayer policy for nasaexoplanet.planets.habitable. 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.

What MCP server provides nasaexoplanet.planets.habitable? +

nasaexoplanet.planets.habitable 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.