Medium Risk

save_document

Save the currently open Word document to the original file (update the original file)

How to control save_document ↓

What save_document does on Doc/docx

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

Medium Risk

Why save_document needs a policy

This tool updates an existing file with modified content, which is a Write operation (reversible data modification). It is not Destructive because the original file version may be recoverable from backups, and the operation itself is not inherently irreversible.

From the tool's definition Tool description states 'Save the currently open Word document to the original file (update the original file)' — this modifies existing data by overwriting the original file with new content.

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

How to control save_document

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

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

save_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 Doc/docx — 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.

Related tools and policies

Go deeper

Questions about save_document

What does the save_document tool do? +

Save the currently open Word document to the original file (update the original file). It is categorised as a Write tool in the Doc/docx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_document? +

Register the Doc/docx MCP server in PolicyLayer and add a rule for save_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/docx. Nothing to install.

What risk level is save_document? +

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

Can I rate-limit save_document? +

Yes. Add a rate_limit block to the save_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 save_document completely? +

Set action: deny in the PolicyLayer policy for save_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 save_document? +

save_document is provided by the Doc/docx MCP server (meterlong/mcp-doc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Doc/docx tool call.

Start from Doc/docx, 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.

23 Doc/docx tools catalogued and risk-classified — across an index of 43,000+ 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.