# get_test_suite_results

Fetch a test suite with full per-test results. Returns suite-level status (NEVER_RUN, PENDING, RUNNING, COMPLETED, ERROR), pass rate, last run timestamp, and per-test outcomes (PASS, FAIL, ERROR, TIMEOUT, etc.) with execution times. Accepts suiteUuid directly or suiteName + project identifier.

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

## Facts

- Tool: `get_test_suite_results`
- 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: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why get_test_suite_results is rated Low

This tool retrieves and queries existing test suite results data. It performs no modifications, deletions, or execution of tests themselves (run_test_suite handles that). The blast radius is minimal—misuse would only expose test data already stored in the system, with no capacity to alter state or trigger external operations.

From the tool's own definition: "The tool 'Fetch[es] a test suite with full per-test results' and 'Returns suite-level status...per-test outcomes...execution times.' The verb 'Fetch' and 'Returns' indicate data retrieval only. No mutations, deletions, or external side effects are performed."

## Use case

AI agents call get_test_suite_results to retrieve information from Debugg AI MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_test_suite_results": {}
  }
}
```

## 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
- `run_test_suite` — Execute — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/run-test-suite.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