document.convert.from_pdf
Convert PDF to Word (DOCX), Excel (XLSX), PowerPoint (PPTX), plain text (TXT), or images (JPG/PNG per page). Optional page range selection. Provide PDF as URL (ConvertAPI)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/document.convert.from-pdf.md
What document.convert.from_pdf does on Apibase
AI agents invoke document.convert.from_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 |
|---|---|---|---|
pages | string | — | Page range to convert (e.g. "1-5", "1,3,5", default "all") |
to_format | string | Yes | Target format to convert PDF into |
source_url | string | Yes | Publicly accessible URL of the PDF to convert (e.g. "https://example.com/doc.pdf") |
Parameters from the server's own tool schema.
Why document.convert.from_pdf is rated High
Triggers external conversion operation producing new files from input PDF.
From the tool's definition Convert PDF to Word, Excel, PowerPoint, plain text, or images
Attacks that exploit this kind of access
The rule that runs document.convert.from_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.from_pdf, this is the rule to start with:
document.convert.from_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.from_pdf call is checked against it from then on.
Questions about document.convert.from_pdf
Convert PDF to Word (DOCX), Excel (XLSX), PowerPoint (PPTX), plain text (TXT), or images (JPG/PNG per page). Optional page range selection. Provide PDF as URL (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.from_pdf accepts 3 parameters: pages, to_format, source_url. Required: to_format, source_url. 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.from_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.from_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.from_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.from_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.from_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