close_document

Close a document and clean up temporary files.

SERVERDocx SOURCEsecurityronin/docx-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/securityronin-docx-mcp/close-document.md

WHAT IT DOES

What close_document does on Docx

AI agents use close_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.

RISK

Why close_document is rated Medium

Closing a document and cleaning up temporary files constitutes state modification of the application and document metadata without irreversible data destruction. This is a Write-level action rather than Read (no data retrieval), Execute (no external command execution), or Destructive (does not delete the actual document file).

From the tool's definition Tool description states 'Close a document and clean up temporary files.' Closing a document can modify application state and temporary file metadata.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs close_document safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Docx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For close_document, this is the rule to start with:

close_document Rate-limited

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.

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every close_document call is checked against it from then on.

FAQ

Questions about close_document

What does the close_document tool do? +

Close a document and clean up temporary files. 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 close_document? +

Register the Docx 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 Docx. 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 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.

KEEP EXPLORING

More on Docx, and thousands of servers like it.

This server

All 219 Docx tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →