solarsystem_body

Get detailed info about a specific solar system body.

SERVERUnClick SOURCE@unclick/mcp-server

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/solarsystem-body.md

WHAT IT DOES

What solarsystem_body does on UnClick

AI agents call solarsystem_body 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
`id`	string	Yes	Body ID (e.g. 'terre' for Earth, 'mars', 'jupiter', 'lune' for Moon).

Parameters from the server's own tool schema.

RISK

Why solarsystem_body is rated Low

This tool queries astronomical data about celestial bodies (planets, moons, asteroids, etc.) and returns information. It performs a read-only lookup with no capability to modify, delete, execute code, or commit financial transactions. The blast radius of misuse is minimal—an agent cannot cause harm by requesting solar system information.

From the tool's definition Tool name 'solarsystem_body' and description 'Get detailed info about a specific solar system body' indicate a data retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs solarsystem_body 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_body, this is the rule to start with:

solarsystem_body Allowed

solarsystem_body 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": {
    "solarsystem_body": {}
  }
}

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

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

FAQ

Questions about solarsystem_body

What does the solarsystem_body tool do? +

Get detailed info about a specific solar system body. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.

What parameters does solarsystem_body accept? +

solarsystem_body accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on solarsystem_body? +

Register the UnClick MCP server in PolicyLayer and add a rule for solarsystem_body: 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.

What risk level is solarsystem_body? +

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

Can I rate-limit solarsystem_body? +

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

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

solarsystem_body 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.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

emit_exploit_body on 0sec → The MCP Attack Database →

Guides

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