Test Design — list all field definitions for test cases in a project, including each field\
AI agents call list-test-case-fields 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 queries and retrieves metadata about test case field definitions. It performs a read-only operation with no side effects, no code execution, no data creation, modification, or deletion. The blast radius of misuse is minimal—an agent listing field definitions cannot harm test data or systems. Classification: Read (low severity).
From the tool's definition Tool name 'list-test-case-fields' and description 'list all field definitions for test cases in a project' indicate a retrieval operation with no data modification.
Attacks that exploit this kind of access
Test Design — list all field definitions for test cases in a project, including each field\. 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-case-fields: 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-case-fields 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-case-fields 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-case-fields. 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-case-fields 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 →