This record as markdown: /tools/com-local-mcp-local-mcp/word-create.md
What word_create does on Local
AI agents use word_create to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Output path for the .docx file |
title | string | — | Document title (optional) |
confirm | boolean | — | Must be true to create |
content | string | Yes | Document text content |
Parameters from the server's own tool schema.
Why word_create is rated Medium
This tool creates new documents, which is a reversible write operation. It does not delete or overwrite existing files (which would be Destructive), nor does it execute arbitrary code or trigger external operations with argument-dependent effects (Execute).
From the tool's definition Tool name 'word_create' and description 'Creates a new Word (.docx) document with the given content' explicitly indicates creation of a new file with user-supplied content.
Risk signalsAccepts file system path (path) · Accepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs word_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For word_create, this is the rule to start with:
word_create 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 Local, apply this rule, and every word_create call is checked against it from then on.
Questions about word_create
Creates a new Word (.docx) document with the given content. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
word_create accepts 4 parameters: path, title, confirm, content. Required: path, content. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for word_create: 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 Local. Nothing to install.
word_create 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 word_create 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 word_create. 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.
word_create is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue