This record as markdown: /tools/com-geekflare-mcp/url2pdf.md
What url2Pdf does on Mcp
AI agents invoke url2Pdf to trigger actions in Mcp. 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 | Target URL |
scale | number | — | Zoom level (0–2) |
device | string | — | |
format | string | — | |
margin | object | — | |
hideCookie | boolean | — | |
orientation | string | — | |
skipCaptcha | boolean | — | |
addTimestamp | boolean | — | |
proxyCountry | string | — | Country code for proxy routing |
Parameters from the server's own tool schema.
Why url2Pdf is rated High
This tool executes an external process: it fetches a remote URL and renders its content into a PDF document. This is not a simple read (it involves rendering and file generation) nor purely destructive, but it executes an external operation whose effects depend on the URL argument. Misuse could involve fetching malicious URLs, generating PDFs of sensitive internal pages, or causing SSRF-like behavior.
From the tool's definition Convert a URL to PDF — triggers an external operation (fetching a URL and rendering it to PDF)
Risk signalsAccepts URL/endpoint input (url) · High parameter count (14 properties)
Attacks that exploit this kind of access
The rule that runs url2Pdf safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For url2Pdf, this is the rule to start with:
url2Pdf 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 Mcp, apply this rule, and every url2Pdf call is checked against it from then on.
Questions about url2Pdf
Convert a URL to PDF. It is categorised as a Execute tool in the Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
url2Pdf accepts 10 parameters: url, scale, device, format, margin, hideCookie, orientation, skipCaptcha, addTimestamp, proxyCountry. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for url2Pdf: 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 Mcp. Nothing to install.
url2Pdf 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 url2Pdf 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 url2Pdf. 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.
url2Pdf is provided by the MCP server (@geekflare/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue