This record as markdown: /tools/cowork-os/browser-save-pdf.md
What browser_save_pdf does on CoWork OS
AI agents use browser_save_pdf to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.
Why browser_save_pdf is rated Medium
The tool creates (writes) a file artifact without permanently destroying data or executing arbitrary code. The action is reversible—saved PDFs can be deleted or overwritten. It does not move money, execute scripts, or irreversibly delete data. Low severity because saving a PDF has minimal blast radius; the worst case is unwanted local file creation, which is easily remediated.
From the tool's definition Tool description states 'Save the current page as a PDF' — this creates a new file (PDF) on the local system.
Attacks that exploit this kind of access
The rule that runs browser_save_pdf safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_save_pdf, this is the rule to start with:
browser_save_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.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every browser_save_pdf call is checked against it from then on.
Questions about browser_save_pdf
Save the current page as a PDF. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CoWork OS MCP server in PolicyLayer and add a rule for browser_save_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 CoWork OS. Nothing to install.
browser_save_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 browser_save_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 browser_save_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.
browser_save_pdf is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue