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.
This record as markdown: /tools/debugg-ai-debugg-ai-mcp/get-test-suite-results.md
What get_test_suite_results does on Debugg AI MCP
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.
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 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.
Attacks that exploit this kind of access
The rule that runs get_test_suite_results 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 get_test_suite_results, this is the rule to start with:
get_test_suite_results 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 get_test_suite_results call is checked against it from then on.
Questions about 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. 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 get_test_suite_results: 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.
get_test_suite_results 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 get_test_suite_results 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 get_test_suite_results. 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.
get_test_suite_results 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