document.convert.to_pdf
Convert Word (DOCX), Excel (XLSX), PowerPoint (PPTX), HTML, Markdown, RTF, ODT, or images (JPG/PNG/SVG) to PDF. Provide source file as URL. Custom page size and orientation. 200+ format pairs supported (ConvertAPI)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/document.convert.to-pdf.md
What document.convert.to_pdf does on Apibase
AI agents invoke document.convert.to_pdf to trigger actions in Apibase. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
page_size | string | — | PDF page size (default "a4") |
source_url | string | Yes | Publicly accessible URL of the source file to convert (e.g. "https://example.com/report.docx") |
from_format | string | Yes | Source file format |
orientation | string | — | Page orientation (default "portrait") |
Parameters from the server's own tool schema.
Why document.convert.to_pdf is rated High
Triggers external conversion operation on a provided file URL, producing a new document.
From the tool's definition Convert... source file as URL... 200+ format pairs supported
Attacks that exploit this kind of access
The rule that runs document.convert.to_pdf safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For document.convert.to_pdf, this is the rule to start with:
document.convert.to_pdf 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every document.convert.to_pdf call is checked against it from then on.
Questions about document.convert.to_pdf
Convert Word (DOCX), Excel (XLSX), PowerPoint (PPTX), HTML, Markdown, RTF, ODT, or images (JPG/PNG/SVG) to PDF. Provide source file as URL. Custom page size and orientation. 200+ format pairs supported (ConvertAPI). It is categorised as a Execute tool in the Apibase MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
document.convert.to_pdf accepts 4 parameters: page_size, source_url, from_format, orientation. Required: source_url, from_format. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for document.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 Apibase. Nothing to install.
document.convert.to_pdf is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the document.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 document.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.
document.convert.to_pdf is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
Across the catalogue