solar.system.body_details
Get comprehensive data for a solar system body — mass, radius, density, gravity, escape velocity, temperature, axial tilt, orbital period, semi-major axis, eccentricity, inclination, discoverer, and list of moons. Source: Solar System OpenData.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/solar.system.body-details.md
What solar.system.body_details does on Apibase
AI agents call solar.system.body_details 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 |
|---|---|---|---|
id | string | Yes | Body ID from search results (e.g. "mars", "jupiter", "moon", "europa", "ceres") |
Parameters from the server's own tool schema.
Why solar.system.body_details is rated Low
Tool retrieves immutable astronomical data with no side effects or system impact.
From the tool's definition Get comprehensive data for a solar system body — mass, radius, density, gravity, escape velocity
Attacks that exploit this kind of access
The rule that runs solar.system.body_details 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 solar.system.body_details, this is the rule to start with:
solar.system.body_details 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 solar.system.body_details call is checked against it from then on.
Questions about solar.system.body_details
Get comprehensive data for a solar system body — mass, radius, density, gravity, escape velocity, temperature, axial tilt, orbital period, semi-major axis, eccentricity, inclination, discoverer, and list of moons. Source: Solar System OpenData. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
solar.system.body_details accepts 1 parameter: id. Required: 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 solar.system.body_details: 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.
solar.system.body_details 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 solar.system.body_details 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 solar.system.body_details. 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.
solar.system.body_details 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