Close an open document and release its resources (including any temp files from format bridging).
AI agents use document_close to create or update resources in LibreOffice MCP Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LibreOffice MCP Tools environment.
document_close modifies application state by closing documents and releasing resources, making it a Write-category operation rather than Read. The blast radius is minimal because closing documents is reversible (user can reopen), non-destructive (no data loss occurs), and typically requires prior context of opened documents.
From the tool's definition Tool performs state-changing operation 'Close an open document and release its resources' which modifies the application state by closing and cleaning up document resources.
Attacks that exploit this kind of access
Close an open document and release its resources (including any temp files from format bridging). It is categorised as a Write tool in the LibreOffice MCP Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LibreOffice MCP Tools MCP server in PolicyLayer and add a rule for document_close: 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 LibreOffice MCP Tools. Nothing to install.
document_close 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 document_close 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 document_close. 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.
document_close is provided by the LibreOffice MCP Tools MCP server (passerbyflutter/libreoffice-mcp-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →