Generate a PDF of the current page
AI agents use generate_pdf to create or update resources in Pydoll — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pydoll environment.
This tool creates a new file (PDF) on the system, which is a reversible write operation. While PDFs can be deleted, the act of generation itself is a write action. Severity is medium rather than high because PDF generation has limited blast radius—it consumes disk space and could be used to exfiltrate visible page content, but does not delete data, execute arbitrary code, or directly compromise financial systems.
From the tool's definition Tool name 'generate_pdf' and description 'Generate a PDF of the current page' indicate creation of a new file artifact from existing content.
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 Pydoll, 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": 30,
"scope": "grant"
}
]
}
}
}generate_pdf stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate a PDF of the current page. It is categorised as a Write tool in the Pydoll MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pydoll 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 Pydoll. Nothing to install.
generate_pdf is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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 Pydoll MCP server (jinsongroh/pydoll-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pydoll, 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.
57 Pydoll tools catalogued and risk-classified — across an index of 43,000+ MCP servers.