Create a Word document directly from content with beautiful formatting. This tool is specifically designed for creating Word documents from scratch, avoiding conversion loops. Supports HTML content with automatic styling and formatting. Output directory is controlled by OUTPUT_DIR environment var...
AI agents use create_word_document to create or update resources in Doc Ops — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Doc Ops environment.
The tool creates new document files with content and formatting, which is a write operation that modifies the file system by adding new data. It does not execute arbitrary code, delete data, move money, or irreversibly destroy content. The severity is low because creating documents has minimal blast radius—the worst case involves generating unwanted files in the OUTPUT_DIR, which can be easily deleted.
From the tool's definition Tool description explicitly states 'Create a Word document' and 'creating Word documents from scratch' with automatic file saving. This is a creation operation that generates new files.
Documented attack patterns abuse exactly the kind of access create_word_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Doc Ops, and nothing reaches the server without passing your rules. This is the rule we recommend for create_word_document:
{
"version": "1",
"default": "deny",
"tools": {
"create_word_document": {
"limits": [
{
"counter": "create_word_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_word_document 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.
Create a Word document directly from content with beautiful formatting. This tool is specifically designed for creating Word documents from scratch, avoiding conversion loops. Supports HTML content with automatic styling and formatting. Output directory is controlled by OUTPUT_DIR environment variable. Files will be automatically saved to OUTPUT_DIR with auto-generated names. It is categorised as a Write tool in the Doc Ops MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Doc Ops MCP server in PolicyLayer and add a rule for create_word_document: 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 Doc Ops. Nothing to install.
create_word_document 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 create_word_document 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 create_word_document. 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.
create_word_document is provided by the Doc Ops MCP server (tele-ai/doc-ops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Doc Ops tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 Doc Ops tools catalogued and risk-classified — across an index of 42,500+ MCP servers.