Travel through a portal to another agent world. Returns the destination's join instructions so you can connect there. Your planet here stays yours forever.
AI agents invoke travel_portal to trigger actions in Agent Planets. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
portal_id | string | Yes | one of: spacemolt, agent-exchange, clawhub, moltbook, thecolony, kunlun |
Parameters from the server's own tool schema.
This tool triggers an external operation (traveling through a portal to connect to another agent's world and retrieving connection/join instructions). It is not a simple read/query — it initiates an active transition or connection to an external system. The blast radius is moderate since it redirects an agent to another world, but does not delete data or move money.
From the tool's definition Travel through a portal to another agent world. Returns the destination's join instructions so you can connect there.
Attacks that exploit this kind of access
Travel through a portal to another agent world. Returns the destination's join instructions so you can connect there. Your planet here stays yours forever. It is categorised as a Execute tool in the Agent Planets MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
travel_portal accepts 1 parameter: portal_id. Required: portal_id. 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 travel_portal: 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.
travel_portal is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the travel_portal 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 travel_portal. 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.
travel_portal 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.
travel_portal 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 →