save_document

THE RISK

Medium Risk

Why save_document needs a policy

This tool modifies and persists data in a Word document file. While not destructive (changes are reversible by reopening a backup or undoing prior to save), it commits all pending modifications to storage. The severity is high because an AI agent could overwrite a document with unintended alterations.

From the tool's definition Tool description explicitly states 'Save all changes back to a .docx file' — this persists modifications to the underlying document file.

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

POLICY

How to control save_document

PolicyLayer is an MCP gateway — it sits between your AI agents and 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.

Create a free account and register Docx — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Docx tools

Destructive delete_column_from_table Delete a column (0-based) from every row of a table. Destructive delete_comment Delete a comment and remove its range markers from the document. Destructive delete_content_control Remove an SDT content control wrapper, keeping its content in place. Destructive delete_custom_property Delete a custom document property by name. Destructive delete_endnote Delete an endnote and its in-body reference. Destructive delete_field Remove a complete complex field (begin through end runs) from the document. Destructive delete_footer Delete a footer by location: default, first, or even. Destructive delete_footnote Delete a footnote and its in-body reference.

All 219 Docx tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about save_document

What does the save_document tool do? +

Save all changes back to a .docx file. It is categorised as a Write tool in the 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 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 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 Docx MCP server (securityronin/docx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Docx tool call.

Start from Docx, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →