AI agents invoke generate_pdf to trigger actions in Browserless 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.
Generating a PDF requires executing a headless browser session, potentially fetching arbitrary URLs or rendering HTML content. This is an external operation that goes beyond simple reads; it executes browser automation logic.
From the tool's definition 'Generate PDF from URL or HTML content' — triggers browser automation to render and produce a PDF file, which is an external operation with side effects (file generation, network requests to arbitrary URLs).
Documented attack patterns abuse exactly the kind of access generate_pdf gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Browserless MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_pdf:
{
"version": "1",
"default": "deny",
"tools": {
"generate_pdf": {
"limits": [
{
"counter": "generate_pdf_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}generate_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.
Free to start. No card required.
Generate PDF from URL or HTML content. It is categorised as a Execute tool in the Browserless MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Browserless MCP Server MCP server in PolicyLayer and add a rule for generate_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 Browserless MCP Server. Nothing to install.
generate_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 generate_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 generate_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.
generate_pdf is provided by the Browserless MCP Server MCP server (lizzard-solutions/browserless-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Browserless MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Browserless MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.