document.convert.web_to_pdf
Render any web page URL to PDF with full JavaScript execution — custom viewport width, lazy content loading, wait delay. Returns PDF download URL (ConvertAPI)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/document.convert.web-to-pdf.md
What document.convert.web_to_pdf does on Apibase
AI agents invoke document.convert.web_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 |
|---|---|---|---|
url | string | Yes | Web page URL to render as PDF (e.g. "https://example.com") |
delay | integer | — | Seconds to wait after page load before capturing (default 0) |
viewport_width | integer | — | Browser viewport width in pixels (default 1280) |
load_lazy_content | boolean | — | Scroll page to trigger lazy-loaded images (default false) |
Parameters from the server's own tool schema.
Why document.convert.web_to_pdf is rated High
Executes JavaScript on arbitrary URLs, triggering external browser-like operations with unpredictable side effects.
From the tool's definition Render any web page URL to PDF with full JavaScript execution
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs document.convert.web_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.web_to_pdf, this is the rule to start with:
document.convert.web_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.web_to_pdf call is checked against it from then on.
Questions about document.convert.web_to_pdf
Render any web page URL to PDF with full JavaScript execution — custom viewport width, lazy content loading, wait delay. Returns PDF download 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.web_to_pdf accepts 4 parameters: url, delay, viewport_width, load_lazy_content. Required: 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.web_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.web_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.web_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.web_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.web_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