Orbit_Ship
AI agents invoke Orbit_Ship to trigger actions in SpaceTraders MCP Server. 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.
Based on the tool name and context of sibling tools (Dock_Ship, Extract_Resources, etc.), Orbit_Ship likely triggers an external operation to change a ship's status/position to orbit, which is an action with side effects on the game state. Since the description is empty, confidence is lowered.
From the tool's definition Tool name 'Orbit_Ship' on a server managing fleets and ship operations; description is empty and uninformative.
Attacks that exploit this kind of access
Orbit_Ship. It is categorised as a Execute tool in the SpaceTraders MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SpaceTraders MCP Server MCP server in PolicyLayer and add a rule for Orbit_Ship: 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 SpaceTraders MCP Server. Nothing to install.
Orbit_Ship 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 Orbit_Ship 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 Orbit_Ship. 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.
Orbit_Ship is provided by the SpaceTraders MCP Server MCP server (thevalverde/spacetraders-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →