convert_to_pdf
Convert the open document to PDF using LibreOffice headless.
This record as markdown: /tools/securityronin-docx-mcp/convert-to-pdf.md
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.
Why convert_to_pdf is rated Medium
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.
Attacks that exploit this kind of access
The rule that runs convert_to_pdf safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For convert_to_pdf, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every convert_to_pdf call is checked against it from then on.
Questions about convert_to_pdf
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.
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.
convert_to_pdf is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on Docx, and thousands of servers like it.
This server
Across the catalogue