# search_test_suites

List and search test suites for a project. Returns paginated results with suite status, test counts, pass rates, and last run timestamps. Requires a project identifier (projectUuid or projectName). Optional: search text filter, page, pageSize (1-100, default 20).

Agent View of the PolicyLayer registry record for `search_test_suites`. HTML page: https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/search-test-suites

## Facts

- Tool: `search_test_suites`
- 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": "search_test_suites",
    "arguments": {}
  }
}
```

## Why search_test_suites is rated Low

This tool retrieves and queries test suite metadata without side effects. It performs listing and searching operations only, which are characteristic of Read category tools. The presence of destructive tools (delete_test_suite, delete_test_case) and executable tools (run_test_suite) on the same server confirms this tool is distinctly a retrieval operation with minimal security risk.

From the tool's own definition: "Tool description states: 'List and search test suites' and 'Returns paginated results' with no modification, deletion, or execution capabilities mentioned. The parameters are all read-only filters (search text, pagination)."

## Use case

AI agents call search_test_suites 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": {
    "search_test_suites": {}
  }
}
```

## 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
- `get_test_suite_results` — Read — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/get-test-suite-results.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