Test Execution — add test cases as test runs into a qTest Test Execution suite (inside a test cycle)
AI agents use add-test-cases to create or update resources in qTest MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your qTest MCP Server environment.
The tool creates or adds test case records into an execution suite, which is a reversible data modification. It does not execute tests, delete data, or move financial resources. While it affects test execution workflows, the core action is creating/adding records (Write category).
From the tool's definition Tool description states it 'add test cases as test runs into a qTest Test Execution suite' — this is a creation/modification operation that adds data to an execution suite.
Attacks that exploit this kind of access
Test Execution — add test cases as test runs into a qTest Test Execution suite (inside a test cycle). It is categorised as a Write tool in the qTest MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the qTest MCP Server MCP server in PolicyLayer and add a rule for add-test-cases: 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 qTest MCP Server. Nothing to install.
add-test-cases 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 add-test-cases 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 add-test-cases. 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.
add-test-cases is provided by the qTest MCP Server MCP server (usman-ghani123/qtest-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →