Medium Risk

close_document

关闭Word文档,可选是否保存更改。 Args: file_path: Word文档的完整路径或相对于输出目录的路径 save_changes: 是否保存更改,默认为True Returns: 操作结果信息

How to control close_document ↓

AI agents use close_document to create or update resources in Office Editor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Office Editor environment.

Medium Risk

Closing a document with save_changes=True modifies the document file on disk by persisting any in-memory edits. This is a reversible write operation. Not Destructive because the document is not deleted—only modifications are saved. Not Read because it has side effects.

From the tool's definition Tool closes a Word document with optional save parameter (save_changes: default True). The description indicates it can persist changes to disk: '是否保存更改' (whether to save changes), with default behavior saving modifications.

Documented attack patterns abuse exactly the kind of access close_document gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Office Editor, and nothing reaches the server without passing your rules. This is the rule we recommend for close_document:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "close_document": {
      "limits": [
        {
          "counter": "close_document_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

close_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.

  1. Create a free account and register Office Editor — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the close_document tool do? +

关闭Word文档,可选是否保存更改。 Args: file_path: Word文档的完整路径或相对于输出目录的路径 save_changes: 是否保存更改,默认为True Returns: 操作结果信息. It is categorised as a Write tool in the Office Editor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on close_document? +

Register the Office Editor MCP server in PolicyLayer and add a rule for close_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 Office Editor. Nothing to install.

What risk level is close_document? +

close_document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit close_document? +

Yes. Add a rate_limit block to the close_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.

How do I block close_document completely? +

Set action: deny in the PolicyLayer policy for close_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.

What MCP server provides close_document? +

close_document is provided by the Office Editor MCP server (thewdy/office-editor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Office Editor tool call.

Deterministic rules across all 88 Office Editor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

88 Office Editor tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.