Open a document in LibreOffice GUI for live viewing Args: path: Path to the document to open readonly: Whether to open in read-only mode (default: False)
AI agents invoke open_document_in_libreoffice to trigger actions in LibreOffice MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an external process (opens the LibreOffice GUI application), which constitutes running an external operation. It's not purely reading data — it launches a GUI application on the host system. The readonly flag indicates it can also open in editable mode, potentially allowing user-driven modifications. Misuse could expose sensitive documents or consume system resources, warranting medium severity.
From the tool's definition 'Open a document in LibreOffice GUI for live viewing' — triggers an external application (LibreOffice GUI) to launch and open a file
Documented attack patterns abuse exactly the kind of access open_document_in_libreoffice gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LibreOffice MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for open_document_in_libreoffice:
{
"version": "1",
"default": "deny",
"tools": {
"open_document_in_libreoffice": {
"limits": [
{
"counter": "open_document_in_libreoffice_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} open_document_in_libreoffice stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Open a document in LibreOffice GUI for live viewing Args: path: Path to the document to open readonly: Whether to open in read-only mode (default: False). It is categorised as a Execute tool in the LibreOffice MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the LibreOffice MCP Server MCP server in PolicyLayer and add a rule for open_document_in_libreoffice: 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 Server. Nothing to install.
open_document_in_libreoffice is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the open_document_in_libreoffice 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 open_document_in_libreoffice. 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.
open_document_in_libreoffice is provided by the LibreOffice MCP Server MCP server (patrup/mcp-libre). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 LibreOffice MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 LibreOffice MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.