track_changes · LibreOffice MCP Server MCP: Risk & Policy

WHAT IT DOES

What track_changes does on LibreOffice MCP Server

AI agents use track_changes to create or update resources in LibreOffice MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LibreOffice MCP Server environment.

WHY IT NEEDS A POLICY

Why track_changes needs a policy

Track changes in LibreOffice is a feature that records modifications to documents (insertions, deletions, formatting changes) while preserving the original content. This is reversible editing functionality—changes can be accepted, rejected, or viewed as a history. It creates or modifies document state but does not irreversibly destroy data or execute arbitrary code.

From the tool's definition Tool is named 'track_changes' and located on a LibreOffice document server described as enabling 'create, read, edit, and manipulate LibreOffice documents with support for track changes.' The server's description explicitly mentions track changes as a feature…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

track_changes Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "track_changes": {
      "limits": [
        {
          "counter": "track_changes_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 track_changes

What does the track_changes tool do? +

track_changes. It is categorised as a Write tool in the LibreOffice MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on track_changes? +

Register the LibreOffice MCP Server MCP server in PolicyLayer and add a rule for track_changes: 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 track_changes? +

track_changes is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit track_changes? +

Yes. Add a rate_limit block to the track_changes 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 track_changes completely? +

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

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