Insert a Table of Tables field block after the paragraph with para_id.
AI agents use generate_tot 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.
The tool modifies a Word document by inserting a new field element (Table of Tables) at a specific location. This is reversible via standard undo functionality or by accepting/rejecting changes in tracked mode. It does not execute arbitrary code, delete content, or trigger financial transactions. It falls squarely into the Write category as it creates new document structure.
From the tool's definition Tool description states it will 'Insert a Table of Tables field block', which creates or adds new content to the document. The verb 'Insert' and the action of adding a field block to a document constitute a write/modification operation.
Documented attack patterns abuse exactly the kind of access generate_tot 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 generate_tot:
{
"version": "1",
"default": "deny",
"tools": {
"generate_tot": {
"limits": [
{
"counter": "generate_tot_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}generate_tot 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.
Insert a Table of Tables field block after the paragraph with para_id. 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 generate_tot: 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.
generate_tot 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 generate_tot 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 generate_tot. 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.
generate_tot 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.