save_document · Docx MCP: Risk & Policy

WHAT IT DOES

What save_document does on Docx

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

WHY IT NEEDS A POLICY

Why save_document needs a policy

This tool writes data to disk, which is reversible (files can be deleted or edited), so it is Write rather than Destructive. However, it has medium severity because uncontrolled file writing could fill storage, overwrite important documents, or create files in sensitive locations. The confidence is high because the name and description clearly indicate file-writing behavior.

From the tool's definition save_document with description 'Save the document to disk' - commits document data to persistent storage, creating or overwriting files on the filesystem.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_document Rate-limited

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.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Docx, so you can run agents against it safely.

FAQ

Questions about save_document

What does the save_document tool do? +

Save the document to disk. 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 (jamesmehorter/mcp-server-docx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.