Close a document and clean up temporary files.
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.
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.
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 Docx, and nothing reaches the server without passing your rules. This is the rule we recommend for close_document:
{
"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.
Free to start. No card required.
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.
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.
close_document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
Start from 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.
219 Docx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.