Open or create a Word document.
AI agents use open_document to create or update resources in DOCX-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DOCX-MCP environment.
Opening an existing document is a Read operation, but the capability to 'create' a Word document as stated in the tool description makes this a Write operation since it results in creating new data/files. The severity is medium because misuse could create unwanted documents or overwrite existing ones, but the impact is limited to document creation rather than financial or destructive data loss. Confidence is high (0.
From the tool's definition Tool name 'open_document' combined with server description stating 'document creation, editing, and saving' indicates the tool can both open existing documents and create new ones. Creating a document is a write operation that modifies the file system state.
Documented attack patterns abuse exactly the kind of access open_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DOCX-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for open_document:
{
"version": "1",
"default": "deny",
"tools": {
"open_document": {
"limits": [
{
"counter": "open_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} open_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.
Open or create a Word document. It is categorised as a Write tool in the DOCX-MCP 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 open_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-MCP. Nothing to install.
open_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 open_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 open_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.
open_document is provided by the DOCX- MCP server (rookie0x80/docx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DOCX-MCP, 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.
16 DOCX-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.