AI agents call project_get_test_case_trees 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 retrieves hierarchical test case tree data from a project. It performs a query operation that returns metadata (tree IDs) for use by other tools downstream, but does not create, modify, delete, or execute any operations. The absence of mutation semantics and side effects clearly places this in the Read category with low severity.
From the tool's definition Tool name is 'project_get_test_case_trees' and description states 'Get test case trees for a project'. The verb 'Get' combined with the read-only nature of retrieving tree structures indicates a data retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get test case trees for a project. Use the returned tree IDs with testcase_list_in_tree. 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 project_get_test_case_trees: 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.
project_get_test_case_trees 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 project_get_test_case_trees 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 project_get_test_case_trees. 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.
project_get_test_case_trees 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 →