run_debug_test · AutoSpectra MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_debug_test does on AutoSpectra MCP Server

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

This tool executes debug tests, which involves running code whose effects depend on test configuration arguments. While not necessarily destructive or financial, it can modify application state, trigger side effects, and its impact depends on what the debug test does. This qualifies as Execute category (runs code/triggers operations) rather than Read (which would be passive inspection).

From the tool's definition Tool name 'run_debug_test' combined with server description indicating 'debugging' and 'testing tools' via MCP protocol. The verb 'run' indicates active execution of code or test procedures.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_debug_test Rate-limited

run_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": {
    "run_debug_test": {
      "limits": [
        {
          "counter": "run_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 run_debug_test

What does the run_debug_test tool do? +

Run a 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 run_debug_test? +

Register the AutoSpectra MCP Server MCP server in PolicyLayer and add a rule for run_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 run_debug_test? +

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

Can I rate-limit run_debug_test? +

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

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

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