Get template details including variables and DSL content.
AI agents call get_template to retrieve information from OpenTester without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves existing template information (details, variables, DSL content). It performs no modifications, deletions, or execution of code. The operation is passive data retrieval, fitting the 'Read' category for query operations that have no side effects on the system state.
From the tool's definition Tool name is 'get_template' and description states it retrieves template details including variables and DSL content. The verb 'Get' and the retrieval-focused description indicate a read operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_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 get_template:
{
"version": "1",
"default": "deny",
"tools": {
"get_template": {}
}
}get_template is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get template details including variables and DSL content. It is categorised as a Read tool in the OpenTester MCP Server, which means it retrieves data without modifying state.
Register the OpenTester MCP server in PolicyLayer and add a rule for get_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.
get_template is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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.