solarsystem_bodies
List solar system bodies (planets, moons, asteroids, comets).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/solarsystem-bodies.md
What solarsystem_bodies does on UnClick
AI agents call solarsystem_bodies to retrieve information from UnClick 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 | number | — | Max results to return. |
filter | string | — | Body type filter: Star, Planet, Dwarf Planet, Asteroid, Comet, Moon. |
Parameters from the server's own tool schema.
Why solarsystem_bodies is rated Low
This tool retrieves astronomical reference data and returns a list of celestial bodies. It performs no data modification, deletion, execution of code, or any action with external consequences. The sole capability is to query and return static information about the solar system, making it a pure Read operation with minimal security risk.
From the tool's definition Tool name is 'solarsystem_bodies' and description states it 'List[s] solar system bodies (planets, moons, asteroids, comets)' — a read-only query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs solarsystem_bodies safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For solarsystem_bodies, this is the rule to start with:
solarsystem_bodies 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 UnClick, apply this rule, and every solarsystem_bodies call is checked against it from then on.
Questions about solarsystem_bodies
List solar system bodies (planets, moons, asteroids, comets). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
solarsystem_bodies accepts 2 parameters: limit, filter. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for solarsystem_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 UnClick. Nothing to install.
solarsystem_bodies 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 solarsystem_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.
Set action: deny in the PolicyLayer policy for solarsystem_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.
solarsystem_bodies is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue