Converts public URL to PDF
AI agents invoke convert_url_to_pdf to trigger actions in PDF Generator API MCP Server. 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.
This tool fetches an arbitrary public URL and converts it to a PDF, constituting an external operation/side effect. It could be misused to probe internal network resources (SSRF) or trigger unintended fetches, making it Execute-level with medium severity.
From the tool's definition 'Converts public URL to PDF' — fetches an external URL and triggers a PDF generation operation, which is an external operation whose effects depend on the URL argument
Attacks that exploit this kind of access
Converts public URL to PDF. It is categorised as a Execute tool in the PDF Generator API MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PDF Generator API MCP Server MCP server in PolicyLayer and add a rule for convert_url_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 PDF Generator API MCP Server. Nothing to install.
convert_url_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 convert_url_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 convert_url_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.
convert_url_to_pdf is provided by the PDF Generator API MCP Server MCP server (pdfgeneratorapi/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →