AI agents use update_template 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.
This tool modifies an existing template within a testing execution system. As a Write operation, it creates or modifies data reversibly without the irreversible consequences of Destructive actions, nor the financial or code-execution impacts of other categories.
From the tool's definition Tool name 'update_template' and description 'Update an existing template' indicate modification of existing data. The action is reversible (templates can be updated again or reverted) and does not permanently delete or destroy data.
Documented attack patterns abuse exactly the kind of access update_template 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 update_template:
{
"version": "1",
"default": "deny",
"tools": {
"update_template": {
"limits": [
{
"counter": "update_template_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_template 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.
Update an existing template. 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 update_template: 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.
update_template 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 update_template 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 update_template. 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.
update_template 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.