Test Execution — list qTest test cycles. Omit all optional args for root-level listing, provide id for a single cycle, or provide name to filter by name (case-insensitive exact match)
AI agents call list-test-cycle 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 only retrieves and lists test cycle data without any side effects. It is a read-only operation that queries existing test cycles, making it a Read category tool with low severity.
From the tool's definition Tool name is 'list-test-cycle' and description states 'list qTest test cycles' with filtering options. No modification, deletion, or execution capability mentioned. It retrieves and queries data with optional filtering parameters (id, name).
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Test Execution — list qTest test cycles. Omit all optional args for root-level listing, provide id for a single cycle, or provide name to filter by name (case-insensitive exact match). 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-cycle: 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-cycle 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-cycle 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-cycle. 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-cycle 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 →