AI agents use testmo_batch_create_cases to create or update resources in Testmo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Testmo environment.
This tool creates test cases in bulk within a test management system. Creation is a Write operation (reversible via deletion), though batch operations affecting multiple records elevate severity to medium due to potential for unintended bulk data creation. The empty description reduces confidence slightly, but the naming convention is sufficiently clear.
From the tool's definition Tool name 'testmo_batch_create_cases' indicates batch creation of test cases. The 'batch' prefix combined with 'create' denotes reversible data creation affecting multiple records.
Attacks that exploit this kind of access
testmo_batch_create_cases. It is categorised as a Write tool in the Testmo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Testmo MCP server in PolicyLayer and add a rule for testmo_batch_create_cases: 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 Testmo. Nothing to install.
testmo_batch_create_cases 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 testmo_batch_create_cases 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 testmo_batch_create_cases. 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.
testmo_batch_create_cases is provided by the Testmo MCP server (strelec00/testmo-mcp). 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 →