This record as markdown: /tools/securityronin-docx-mcp/create-document.md
What create_document does on Docx
AI agents use create_document 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.
Why create_document is rated Medium
The tool creates new Word documents, a reversible write operation. While document creation is less impactful than destructive operations, it can create files that consume storage or be weaponized in workflows. Confidence is not higher because the tool description is empty, leaving some ambiguity about exact behavior (e.g., whether it requires templates or has guardrails).
From the tool's definition Tool name 'create_document' combined with server description stating it enables 'editing...Microsoft Word documents' and 'OOXML-level document manipulation.' No description provided for this specific tool, but the name and context indicate document creation.
Attacks that exploit this kind of access
The rule that runs create_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_document, this is the rule to start with:
create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every create_document call is checked against it from then on.
Questions about create_document
create_document is a write tool on the Docx MCP server. 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 create_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 Docx. Nothing to install.
create_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_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_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_document 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.
More on Docx, and thousands of servers like it.
This server
Across the catalogue