Test Design — fetch test cases from a qTest module with optional property filters (Type, Status, Priority, version, etc.). Requires moduleId (numeric).
AI agents call list-test-cases to retrieve information from qTest MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries test case data from a qTest module without creating, modifying, deleting, or executing anything. It is a straightforward read operation that returns information based on the provided moduleId and optional filters. The blast radius is minimal—misuse would only expose or retrieve existing test case metadata, which may be sensitive but is non-destructive.
From the tool's definition Tool name 'list-test-cases' and description explicitly states 'fetch test cases' with 'optional property filters'. The verb 'fetch' and the presence of filter parameters indicate a query operation with no side effects.
Attacks that exploit this kind of access
Test Design — fetch test cases from a qTest module with optional property filters (Type, Status, Priority, version, etc.). Requires moduleId (numeric). It is categorised as a Read tool in the qTest MCP Server MCP Server, which means it retrieves data without modifying state.
Register the qTest MCP Server MCP server in PolicyLayer and add a rule for list-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.
list-test-cases 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 list-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 list-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.
list-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 →