Test Design — update properties of an existing test case (Status, Type, Priority, Test Suite).
AI agents use update-test-case-properties 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.
This tool modifies existing test case properties but does not delete or irreversibly destroy data. The changes are reversible (properties can be updated again), making it a Write operation rather than Destructive.
From the tool's definition The tool description explicitly states it 'update[s] properties of an existing test case', which are reversible modifications to test case metadata (Status, Type, Priority, Test Suite).
Attacks that exploit this kind of access
Test Design — update properties of an existing test case (Status, Type, Priority, Test Suite). 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 update-test-case-properties: 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.
update-test-case-properties 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 update-test-case-properties 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 update-test-case-properties. 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.
update-test-case-properties 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 →