Medium Risk

convert_to_pdf

Convert the open document to PDF using LibreOffice headless.

How to control convert_to_pdf ↓

What convert_to_pdf does on Docx

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

Medium Risk

Why convert_to_pdf needs a policy

Converting a document to PDF creates a new file artifact, which is a write operation that modifies the document's state on the system (a new file is generated). While reversible via deletion, it represents creation of data. Not Execute because it doesn't run arbitrary code or shell commands—it invokes a specific LibreOffice conversion operation.

From the tool's definition Tool description states 'Convert the open document to PDF using LibreOffice headless' - this creates a new output file (PDF) from the existing document.

Documented attack patterns abuse exactly the kind of access convert_to_pdf gives an agent:

How to control convert_to_pdf

PolicyLayer is an MCP gateway — it sits between your AI agents and Docx, and nothing reaches the server without passing your rules. This is the rule we recommend for convert_to_pdf:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "convert_to_pdf": {
      "limits": [
        {
          "counter": "convert_to_pdf_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Docx — 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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about convert_to_pdf

What does the convert_to_pdf tool do? +

Convert the open document to PDF using LibreOffice headless. It is categorised as a Write tool in the Docx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on convert_to_pdf? +

Register the Docx MCP server in PolicyLayer and add a rule for convert_to_pdf: 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 Docx. Nothing to install.

What risk level is convert_to_pdf? +

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

Can I rate-limit convert_to_pdf? +

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

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

convert_to_pdf is provided by the Docx MCP server (securityronin/docx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Docx tool call.

Start from Docx, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

219 Docx tools catalogued and risk-classified — across an index of 43,000+ 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.