Low Risk

watch_document_changes

Watch a document for changes and provide live updates Args: path: Path to the document to watch duration_seconds: How long to watch for changes (default: 30 seconds)

How to control watch_document_changes ↓

AI agents call watch_document_changes to retrieve information from LibreOffice MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves or monitors data (document changes) without side effects. It does not create, modify, execute, or delete anything. Watching for changes is a read-only operation with minimal blast radius even if misused by an agent.

From the tool's definition Tool 'watch_document_changes' watches a document for changes and provides live updates. The parameters (path, duration_seconds) indicate passive monitoring only - no modification, execution, or deletion capability. The action is purely observational.

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "watch_document_changes": {}
  }
}

watch_document_changes is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the watch_document_changes tool do? +

Watch a document for changes and provide live updates Args: path: Path to the document to watch duration_seconds: How long to watch for changes (default: 30 seconds). It is categorised as a Read tool in the LibreOffice MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on watch_document_changes? +

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

watch_document_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit watch_document_changes? +

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

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

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