create_test_suite
Create a named test suite for a project. A test suite is a collection of test cases that can be run together. Requires name, description, and a project identifier (projectUuid or projectName). Returns {uuid, name, description, runStatus, testsCount}.
This record as markdown: /tools/debugg-ai-debugg-ai-mcp/create-test-suite.md
What create_test_suite does on Debugg AI MCP
AI agents use create_test_suite to create or update resources in Debugg AI MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Debugg AI MCP environment.
Why create_test_suite is rated Medium
This tool creates new test suite objects in the system. While it modifies state by adding records, the operation is fully reversible (deletion is available via delete_test_suite). There is no irreversible data loss, code execution, or financial impact. The blast radius is limited to test infrastructure metadata, making this a low-severity Write action.
From the tool's definition Tool description states it 'Create[s] a named test suite' and 'Returns {uuid, name, description, runStatus, testsCount}', indicating data creation.
Attacks that exploit this kind of access
The rule that runs create_test_suite 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 create_test_suite, this is the rule to start with:
create_test_suite stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_test_suite call is checked against it from then on.
Questions about create_test_suite
Create a named test suite for a project. A test suite is a collection of test cases that can be run together. Requires name, description, and a project identifier (projectUuid or projectName). Returns {uuid, name, description, runStatus, testsCount}. It is categorised as a Write tool in the Debugg AI MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Debugg AI MCP server in PolicyLayer and add a rule for create_test_suite: 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.
create_test_suite is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_test_suite 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 create_test_suite. 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.
create_test_suite 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