Validate a template and extract its variables
AI agents call validate_template to retrieve information from docxtpl MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The validate_template tool performs template inspection and variable extraction, which are read operations. It does not create, modify, delete data (no Write, Destructive), does not execute code or trigger external operations (no Execute), and involves no financial transactions (no Financial). The action is passive analysis of template metadata, fitting the Read category.
From the tool's definition Tool description states 'Validate a template and extract its variables' — a read-only operation that inspects and reports on template structure without modifying, deleting, or executing any content.
Attacks that exploit this kind of access
Validate a template and extract its variables. It is categorised as a Read tool in the docxtpl MCP Server MCP Server, which means it retrieves data without modifying state.
Register the docxtpl MCP Server MCP server in PolicyLayer and add a rule for validate_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 docxtpl MCP Server. Nothing to install.
validate_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 validate_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 validate_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.
validate_template is provided by the docxtpl MCP Server MCP server (z1w2r3/doc-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 →