continue_debug_test · AutoSpectra MCP Server MCP

WHAT IT DOES

What continue_debug_test does on AutoSpectra MCP Server

AI agents invoke continue_debug_test to trigger actions in AutoSpectra 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.

WHY IT NEEDS A POLICY

Why continue_debug_test needs a policy

This tool resumes execution of a paused debug session, which triggers further code/test execution. It falls under Execute as it runs/continues a process. The blast radius is medium since it could trigger unintended test actions or side effects depending on what the paused test was doing.

From the tool's definition Continue execution of a paused debug test

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

continue_debug_test Rate-limited

continue_debug_test 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": {
    "continue_debug_test": {
      "limits": [
        {
          "counter": "continue_debug_test_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 AutoSpectra MCP Server, so you can run agents against it safely.

FAQ

Questions about continue_debug_test

What does the continue_debug_test tool do? +

Continue execution of a paused debug test. It is categorised as a Execute tool in the AutoSpectra MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on continue_debug_test? +

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

What risk level is continue_debug_test? +

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

Can I rate-limit continue_debug_test? +

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

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

continue_debug_test is provided by the AutoSpectra MCP Server MCP server (raphaenterprises-ai/autospectra-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.