# run_test_suite

Trigger all test cases in a suite to run asynchronously. Accepts suiteUuid directly, or suiteName + project identifier. Optional: targetUrl to override the default test target. Returns {suiteUuid, runStatus, testsTriggered, note}. Use get_test_suite_results to poll for results.

Agent View of the PolicyLayer registry record for `run_test_suite`. HTML page: https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/run-test-suite

## Facts

- Tool: `run_test_suite`
- Server: Debugg AI MCP (`debugg-ai/debugg-ai-mcp`) — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp.md
- Homepage: https://github.com/debugg-ai/debugg-ai-mcp
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "run_test_suite",
    "arguments": {}
  }
}
```

## Why run_test_suite is rated High

This tool executes test cases whose effects depend on configuration arguments (suiteUuid, project identifier, targetUrl). While test execution is typically benign, the ability to redirect tests to arbitrary targetUrls and trigger multiple test cases asynchronously creates a risk of unintended side effects or resource consumption if misused by an AI agent.

From the tool's own definition: "Tool description states it will 'Trigger all test cases in a suite to run asynchronously' and 'Returns {suiteUuid, runStatus, testsTriggered, note}'. The term 'Trigger' combined with 'run asynchronously' indicates execution of external operations (test cases)."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Debugg AI MCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_test_suite": {
      "limits": [
        {
          "counter": "run_test_suite_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Debugg AI MCP (6)

- `delete_test_case` — Destructive — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/delete-test-case.md
- `delete_test_suite` — Destructive — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/delete-test-suite.md
- `get_test_suite_results` — Read — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/get-test-suite-results.md
- `search_test_suites` — Read — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/search-test-suites.md
- `create_test_suite` — Write — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/create-test-suite.md
- `update_test_case` — Write — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/update-test-case.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=debugg-ai-debugg-ai-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/debugg-ai-debugg-ai-mcp