AI agents use testcase_create to create or update resources in Testops — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Testops environment.
This tool creates new test case records in a test management system. It modifies data by adding records reversibly—test cases can be updated or deleted later. It does not execute arbitrary code, delete data irreversibly, or move money. The medium severity reflects that bulk misuse could clutter the test management system, but damage is reversible and limited to test metadata rather than production systems.
From the tool's definition Tool name includes 'create' and description states 'Create a new test case in TestOps' with required parameters name and projectId, plus optional fields. This is a reversible data creation operation.
Attacks that exploit this kind of access
Create a new test case in TestOps. Required: name and projectId. Optional: steps, customFields, tags, precondition, etc. It is categorised as a Write tool in the Testops MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Testops MCP server in PolicyLayer and add a rule for testcase_create: 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_create 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 testcase_create 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_create. 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_create 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 →