High Risk →

refresh_document_in_libreoffice

Send a refresh signal to LibreOffice to reload a document Args: path: Path to the document that should be refreshed

How to control refresh_document_in_libreoffice ↓

AI agents invoke refresh_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.

High Risk

This tool triggers an external operation on a running LibreOffice application by sending a signal to reload a document. It interacts with an external process (LibreOffice) and causes it to perform an action, placing it in the Execute category. Misuse could cause loss of unsaved changes if a document is reloaded unexpectedly, giving it medium severity.

From the tool's definition Send a refresh signal to LibreOffice to reload a document

Documented attack patterns abuse exactly the kind of access refresh_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 refresh_document_in_libreoffice:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "refresh_document_in_libreoffice": {
      "limits": [
        {
          "counter": "refresh_document_in_libreoffice_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

refresh_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.

  1. Create a free account and register LibreOffice MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the refresh_document_in_libreoffice tool do? +

Send a refresh signal to LibreOffice to reload a document Args: path: Path to the document that should be refreshed. 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.

How do I enforce a policy on refresh_document_in_libreoffice? +

Register the LibreOffice MCP Server MCP server in PolicyLayer and add a rule for refresh_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.

What risk level is refresh_document_in_libreoffice? +

refresh_document_in_libreoffice is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit refresh_document_in_libreoffice? +

Yes. Add a rate_limit block to the refresh_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.

How do I block refresh_document_in_libreoffice completely? +

Set action: deny in the PolicyLayer policy for refresh_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.

What MCP server provides refresh_document_in_libreoffice? +

refresh_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.

Enforce policy on every LibreOffice MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.