test_agent · Spaceship MCP: Risk & Policy

WHAT IT DOES

What test_agent does on Spaceship MCP

AI agents invoke test_agent 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 test_agent needs a policy

The name 'test_agent' strongly implies triggering or running an agent in a test capacity, which constitutes execution of external operations. Given the server's stated purpose of 'execution' and 'agent lifecycle management', this tool likely runs an agent. However, the description is empty, reducing confidence.

From the tool's definition Tool name 'test_agent' on a server described as managing and executing AI agents, with sibling tools like 'create_agent', 'delete_agent', and 'list_executions' suggesting agent execution context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_agent Rate-limited

test_agent 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": {
    "test_agent": {
      "limits": [
        {
          "counter": "test_agent_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 test_agent

What does the test_agent tool do? +

test_agent. 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 test_agent? +

Register the Spaceship MCP server in PolicyLayer and add a rule for test_agent: 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 test_agent? +

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

Can I rate-limit test_agent? +

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

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

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