Convert a local HTML file (.html or .htm) to a PDF. The HTML is rendered server-side; external assets referenced by the file may not be fetched.
Part of the Pdf Toolkit server.
Free to start. No card required.
AI agents use html_to_pdf to create or modify resources in Pdf Toolkit. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call html_to_pdf repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Pdf Toolkit.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"html_to_pdf": {
"limits": [
{
"counter": "html_to_pdf_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Pdf Toolkit policy for all 18 tools.
These attack patterns abuse exactly the kind of access html_to_pdf gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Convert a local HTML file (.html or .htm) to a PDF. The HTML is rendered server-side; external assets referenced by the file may not be fetched.. It is categorised as a Write tool in the Pdf Toolkit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pdf Toolkit MCP server in PolicyLayer and add a rule for html_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 Toolkit. Nothing to install.
html_to_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 html_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 html_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.
html_to_pdf is provided by the Pdf Toolkit MCP server (pdf-toolkit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Pdf Toolkit tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.