AI agents use create_document to create or update resources in Doc Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Doc Tools environment.
Creating a document is a reversible write operation. It modifies state by introducing new data into the system, but the action can be undone (document can be deleted). This is less severe than destructive operations (which cannot be reversed) and does not trigger code execution or financial transactions.
From the tool's definition Tool is named 'create_document' on a server described as 'Word document reading and writing MCP'; sibling tools include 'add_paragraph', 'add_table', 'search_and_replace', and 'set_page_margins', all write operations.
Documented attack patterns abuse exactly the kind of access create_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Doc Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for create_document:
{
"version": "1",
"default": "deny",
"tools": {
"create_document": {
"limits": [
{
"counter": "create_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
create_document. It is categorised as a Write tool in the Doc Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Doc Tools 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 Doc Tools. 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 Doc Tools MCP server (puchunjie/doc-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Doc Tools, 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.
7 Doc Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.