Save the current page as a PDF document in A4 format. Use when the user wants to export the page as a downloadable PDF, save a receipt, or archive a page for offline reading. Parameters: - output_path: File path to save the PDF (default: /tmp/pilot-page.pdf). Must be within the allowed output dir...
AI agents use pilot_pdf to create or update resources in Pilot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pilot environment.
The tool's primary function is to write/create a new PDF file in the filesystem. While it involves browser automation context, the actual operation is a reversible write action that produces a file artifact. The severity is low because the blast radius of misuse is limited—an agent saving PDFs is not destructive, does not execute arbitrary code, and does not cause financial harm.
From the tool's definition Tool creates and saves a PDF file to disk at a specified output_path location. The description states 'Save the current page as a PDF document' and 'returns confirmation with the file path where the PDF was saved.' This is file creation/writing, not retrieval…
Documented attack patterns abuse exactly the kind of access pilot_pdf gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pilot, and nothing reaches the server without passing your rules. This is the rule we recommend for pilot_pdf:
{
"version": "1",
"default": "deny",
"tools": {
"pilot_pdf": {
"limits": [
{
"counter": "pilot_pdf_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pilot_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.
Save the current page as a PDF document in A4 format. Use when the user wants to export the page as a downloadable PDF, save a receipt, or archive a page for offline reading. Parameters: - output_path: File path to save the PDF (default: /tmp/pilot-page.pdf). Must be within the allowed output directory Returns: Confirmation with the file path where the PDF was saved. Errors: -. It is categorised as a Write tool in the Pilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pilot MCP server in PolicyLayer and add a rule for pilot_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 Pilot. Nothing to install.
pilot_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 pilot_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 pilot_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.
pilot_pdf is provided by the Pilot MCP server (tacosyhorchata/pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 61 Pilot tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
61 Pilot tools catalogued and risk-classified — across an index of 42,500+ MCP servers.