Generate a PDF of any URL.
AI agents invoke pdf to trigger actions in Mcp Services. 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.
Generating a PDF from a URL involves executing an external rendering process against an arbitrary URL, which constitutes triggering an external operation. While it produces a file (Write-like), the core action is executing a browser/rendering engine against user-supplied URLs, which could be misused for SSRF, internal network scanning, or rendering malicious content. Execute is the most appropriate category.
From the tool's definition "Generate a PDF of any URL" — triggers an external operation (headless browser or rendering engine) that fetches and processes arbitrary URLs, producing a file output.
Attacks that exploit this kind of access
Generate a PDF of any URL. It is categorised as a Execute tool in the Mcp Services MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Services MCP server in PolicyLayer and add a rule for 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 Mcp Services. Nothing to install.
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 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 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.
pdf is provided by the Mcp Services MCP server (san-npm/mcp-services). 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 →