refresh_document_in_libreoffice · LibreOffice MCP Server MCP

WHAT IT DOES

What refresh_document_in_libreoffice does on LibreOffice MCP Server

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.

WHY IT NEEDS A POLICY

Why refresh_document_in_libreoffice needs a policy

This tool triggers an external operation (sending a signal to LibreOffice to reload/refresh a document), which is an Execute-class action. It doesn't merely read data or write content — it actively triggers a runtime operation in the LibreOffice application. Misuse could cause loss of unsaved changes in an open document, but it's not inherently destructive in a permanent sense.

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

refresh_document_in_libreoffice Rate-limited

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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LibreOffice MCP Server, so you can run agents against it safely.

FAQ

Questions about refresh_document_in_libreoffice

What does the refresh_document_in_libreoffice tool do? +

Send a refresh signal to LibreOffice to reload a document. 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 (jwingnut/mcp-libre). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.