New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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)

SERVERApibase SOURCEapibase-mcp-client
High RISK CLASS
Category Execute
Parameters 32 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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

Questions about document.convert.from_pdf

What does the document.convert.from_pdf tool do? +

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.

What parameters does document.convert.from_pdf accept? +

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.

How do I enforce a policy on document.convert.from_pdf? +

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.

What risk level is document.convert.from_pdf? +

document.convert.from_pdf is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit document.convert.from_pdf? +

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.

How do I block document.convert.from_pdf completely? +

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.

What MCP server provides document.convert.from_pdf? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.