AI agents call testcase_list_in_tree to retrieve information from Testops 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 test case data from a project hierarchy without modifying, executing, or deleting anything. It is a straightforward read operation with no side effects. The sibling tools (launch_get, launch_list, project_get_by_id, project_find_by_name) reinforce that this server primarily provides read and query capabilities for test management metadata.
From the tool's definition Tool name 'testcase_list_in_tree' and description 'List test cases under a project tree with pagination' indicate data retrieval only. The verb 'List' and mention of pagination are characteristic of Read operations.
Attacks that exploit this kind of access
List test cases under a project tree with pagination. Use parentNodeId to page into a folder. It is categorised as a Read tool in the Testops MCP Server, which means it retrieves data without modifying state.
Register the Testops MCP server in PolicyLayer and add a rule for testcase_list_in_tree: 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 Testops. Nothing to install.
testcase_list_in_tree 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 testcase_list_in_tree 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 testcase_list_in_tree. 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.
testcase_list_in_tree is provided by the Testops MCP server (@syn7xx/testops-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 →