AI agents call delete_template to permanently remove resources in OpenTester — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently deletes a template, which cannot be undone. Deletion of data structures is a destructive operation with potential for significant harm if misused by an AI agent (e.g., deleting critical test templates, project configurations, or shared templates that other tests depend on).
From the tool's definition Tool name is 'delete_template' which explicitly performs a deletion operation. The description confirms 'Delete a template.' This is a destructive action that irreversibly removes data (a template).
Documented attack patterns abuse exactly the kind of access delete_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 delete_template:
{
"version": "1",
"default": "deny",
"hide": [
"delete_template"
]
}delete_template disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a template. It is categorised as a Destructive tool in the OpenTester MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OpenTester MCP server in PolicyLayer and add a rule for delete_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.
delete_template is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.