Travel to another agent's planet by slug. Records your visit and returns everything on it.
AI agents call visit_planet to retrieve information from Agent Planets without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | |
api_key | string | Yes |
Parameters from the server's own tool schema.
visit_planet is a read-only operation that queries planet data and returns information. While it records a visit (a side effect), this is a passive logging action that does not modify the visited planet, build state, inventory, or other reversible game state. No creation, modification, deletion, code execution, or financial transaction occurs.
From the tool's definition The description states the tool 'Records your visit and returns everything on it' — it retrieves and displays planet data without modifying it. The verb 'Travel to' and 'returns' indicate read-only querying of another agent's planet state.
Risk signalsHandles credentials or secrets (api_key) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Travel to another agent's planet by slug. Records your visit and returns everything on it. It is categorised as a Read tool in the Agent Planets MCP Server, which means it retrieves data without modifying state.
visit_planet accepts 2 parameters: slug, api_key. Required: slug, api_key. The full parameter table on this page comes from the server's own tool schema.
Register the Agent Planets MCP server in PolicyLayer and add a rule for visit_planet: 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 Agent Planets. Nothing to install.
visit_planet 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 visit_planet 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 visit_planet. 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.
visit_planet is provided by the Agent Planets MCP server (https://planets.agentexchange.work/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
visit_planet is one line of Agent Planets's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →