edit_document
Edit an existing Word document (DOCX). Supports append, move_section, insert_after_section, replace_blocks, and list_sections. Use this to modify existing documents without recreating them from scratch.
This record as markdown: /tools/cowork-os/edit-document.md
What edit_document does on CoWork OS
AI agents use edit_document to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.
Why edit_document is rated Medium
The tool creates or modifies data (document content) without deletion capabilities. Operations like append, move, insert, and replace are characteristic of Write category tools. Severity is medium because unintended document modifications could cause information loss or corruption, but changes are typically reversible through undo or version history in most document systems.
From the tool's definition Tool description states 'Edit an existing Word document (DOCX)' with operations including 'append, move_section, insert_after_section, replace_blocks' — these are reversible modifications to existing documents.
Attacks that exploit this kind of access
The rule that runs edit_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For edit_document, this is the rule to start with:
edit_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 CoWork OS, apply this rule, and every edit_document call is checked against it from then on.
Questions about edit_document
Edit an existing Word document (DOCX). Supports append, move_section, insert_after_section, replace_blocks, and list_sections. Use this to modify existing documents without recreating them from scratch. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CoWork OS MCP server in PolicyLayer and add a rule for edit_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 CoWork OS. Nothing to install.
edit_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 edit_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 edit_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.
edit_document is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue