solar.system.bodies

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/solar.system.bodies.md

WHAT IT DOES

What solar.system.bodies does on Apibase

AI agents call solar.system.bodies 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
`body_type`	string	—	Filter by body type: planet, moon, asteroid, comet, dwarf_planet, or all (default: all)

Parameters from the server's own tool schema.

RISK

Why solar.system.bodies is rated Low

Retrieves astronomical data without side effects, dependencies, or operational impact.

From the tool's definition List solar system bodies, returns name, body type, gravity, radius, moon count.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs solar.system.bodies 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.bodies, this is the rule to start with:

solar.system.bodies Allowed

solar.system.bodies is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "solar.system.bodies": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every solar.system.bodies call is checked against it from then on.

FAQ

Questions about solar.system.bodies

What does the solar.system.bodies tool do? +

List solar system bodies — planets, moons, asteroids, comets, dwarf planets. Returns name, body type, gravity, radius, and moon count. 1,400+ bodies. Filter by type. Source: Solar System OpenData (MIT license). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does solar.system.bodies accept? +

solar.system.bodies accepts 1 parameter: body_type. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on solar.system.bodies? +

Register the Apibase MCP server in PolicyLayer and add a rule for solar.system.bodies: 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 solar.system.bodies? +

solar.system.bodies is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit solar.system.bodies? +

Yes. Add a rate_limit block to the solar.system.bodies 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 solar.system.bodies completely? +

Set action: deny in the PolicyLayer policy for solar.system.bodies. 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 solar.system.bodies? +

solar.system.bodies 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →