AI agents call testcase_get_detail 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 and aggregates metadata about a test case (name, description, tags, custom fields, step texts). It performs a read-only query operation with no side effects—no data is created, modified, deleted, or used to trigger external operations. The context of sibling tools (launch_list, launch_get, project_get_by_id) on a test operations server further confirms this is a data retrieval endpoint.
From the tool's definition Tool name 'testcase_get_detail' and description 'Aggregated card: name, description, tags, custom fields, and step texts as a simple list' indicate retrieval of test case information without modification or deletion.
Attacks that exploit this kind of access
Aggregated card: name, description, tags, custom fields, and step texts as a simple list. 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_get_detail: 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_get_detail 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_get_detail 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_get_detail. 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_get_detail 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 →