Render a web page to a PDF document and return the hosted file URL.
AI agents call url_to_pdf to retrieve information from ToolCenter MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though url_to_pdf only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Render a web page to a PDF document and return the hosted file URL. It is categorised as a Read tool in the ToolCenter MCP MCP Server, which means it retrieves data without modifying state.
Register the ToolCenter MCP server in PolicyLayer and add a rule for 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 ToolCenter MCP. Nothing to install.
url_to_pdf is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the 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 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.
url_to_pdf is provided by the ToolCenter MCP server (toolcenter-dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
url_to_pdf is one line of ToolCenter's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →