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).
This record as markdown: /tools/debugg-ai-debugg-ai-mcp/search-test-suites.md
What search_test_suites does on Debugg AI MCP
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.
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 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).
Attacks that exploit this kind of access
The rule that runs search_test_suites safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Debugg AI MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_test_suites, this is the rule to start with:
search_test_suites is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Debugg AI MCP, apply this rule, and every search_test_suites call is checked against it from then on.
Questions about 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). It is categorised as a Read tool in the Debugg AI MCP MCP Server, which means it retrieves data without modifying state.
Register the Debugg AI MCP server in PolicyLayer and add a rule for search_test_suites: 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 Debugg AI MCP. Nothing to install.
search_test_suites is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_test_suites 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.
Set action: deny in the PolicyLayer policy for search_test_suites. 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.
search_test_suites is provided by the Debugg AI MCP server (debugg-ai/debugg-ai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Debugg AI, and thousands of servers like it.
This server
Across the catalogue