AI agents use create_document_from_content 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 is a Write operation because it creates and persists new data (a Word document file) in a reversible manner. While documents could theoretically contain sensitive content an AI agent generates, the tool itself simply creates/writes files without destructive, financial, or code-execution capabilities.
From the tool's definition The tool creates a complete Word document; the description states it will 'Create a complete Word document in a single call', which is document creation/generation.
Attacks that exploit this kind of access
Create a complete Word document in a single call (FAST - use this instead of multiple calls). 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_from_content: 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_from_content 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_from_content 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_from_content. 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_from_content is provided by the Docx MCP server (jamesmehorter/mcp-server-docx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →