Fill SDT content controls from data dict. Keys match w:tag values.
AI agents use fill_template to create or update resources in Docx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docx environment.
This tool creates or modifies document data reversibly by populating template fields. While it transforms document content, the operation does not delete data, execute arbitrary code, or incur financial consequences. It aligns with the Write category as it updates document state in a controlled, non-destructive manner.
From the tool's definition The tool 'fill_template' modifies document content by filling SDT (Structured Document Tags) content controls with data from a dictionary.
Documented attack patterns abuse exactly the kind of access fill_template gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Docx, and nothing reaches the server without passing your rules. This is the rule we recommend for fill_template:
{
"version": "1",
"default": "deny",
"tools": {
"fill_template": {
"limits": [
{
"counter": "fill_template_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}fill_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.
Fill SDT content controls from data dict. Keys match w:tag values. It is categorised as a Write tool in the Docx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Docx MCP server in PolicyLayer and add a rule for fill_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 Docx. Nothing to install.
fill_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 fill_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 fill_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.
fill_template is provided by the Docx MCP server (securityronin/docx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Docx, 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.
219 Docx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.