run_orchestration · Spaceship MCP: Risk & Policy

WHAT IT DOES

What run_orchestration does on Spaceship MCP

AI agents invoke run_orchestration to trigger actions in Spaceship MCP. 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.

WHY IT NEEDS A POLICY

Why run_orchestration needs a policy

This tool executes orchestrations on the Spaceship AI platform—triggering external operations whose effects depend on how the orchestration is configured. While the empty description limits certainty, the context (agent lifecycle management, execution capability) and naming clearly indicate this performs Execute-class actions.

From the tool's definition Tool name 'run_orchestration' combined with server description stating it 'provides comprehensive tools for agent lifecycle management, including creation, execution, and real-time monitoring'. The term 'run' indicates triggering/executing operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_orchestration Rate-limited

run_orchestration stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_orchestration": {
      "limits": [
        {
          "counter": "run_orchestration_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Spaceship MCP, so you can run agents against it safely.

FAQ

Questions about run_orchestration

What does the run_orchestration tool do? +

run_orchestration. It is categorised as a Execute tool in the Spaceship MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_orchestration? +

Register the Spaceship MCP server in PolicyLayer and add a rule for run_orchestration: 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 Spaceship MCP. Nothing to install.

What risk level is run_orchestration? +

run_orchestration is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_orchestration? +

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

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

run_orchestration is provided by the Spaceship MCP server (spaceship-ai/spaceship-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.