AI agents use create_template_from_case to create or update resources in OpenTester — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenTester environment.
The 'create_template_from_case' name suggests generating a test template from an existing test case, which is a write operation that creates new data. This is reversible (templates can be deleted via 'delete_template'), so it falls under Write rather than Destructive.
From the tool's definition Tool name indicates 'create' action; sibling tools include 'delete_template' and 'create_template', suggesting this performs a reversible creation/modification operation. Description is empty, reducing confidence.
Documented attack patterns abuse exactly the kind of access create_template_from_case gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenTester, and nothing reaches the server without passing your rules. This is the rule we recommend for create_template_from_case:
{
"version": "1",
"default": "deny",
"tools": {
"create_template_from_case": {
"limits": [
{
"counter": "create_template_from_case_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_template_from_case stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
create_template_from_case. It is categorised as a Write tool in the OpenTester MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenTester MCP server in PolicyLayer and add a rule for create_template_from_case: 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 OpenTester. Nothing to install.
create_template_from_case 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 create_template_from_case 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 create_template_from_case. 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.
create_template_from_case is provided by the OpenTester MCP server (kznr02/opentester). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenTester, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 OpenTester tools catalogued and risk-classified — across an index of 43,000+ MCP servers.