browser_pdf_save · Playwright MCP: Risk & Policy

WHAT IT DOES

What browser_pdf_save does on Playwright MCP

AI agents use browser_pdf_save to create or update resources in Playwright MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Playwright MCP environment.

WHY IT NEEDS A POLICY

Why browser_pdf_save needs a policy

Saving a PDF is a write operation—it creates or persists data (a file) to the filesystem. It is reversible (the file can be deleted), so it does not qualify as Destructive. It has no financial impact. The severity is medium because an attacker could use this to exfiltrate sensitive web content rendered as PDFs, or to fill storage; however, the impact depends on what content is captured.

From the tool's definition Tool name 'browser_pdf_save' indicates saving/exporting PDF content. Description is empty, limiting direct confirmation, but the action of saving a PDF file to storage is a write operation that creates a new file artifact.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_pdf_save Rate-limited

browser_pdf_save 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_pdf_save": {
      "limits": [
        {
          "counter": "browser_pdf_save_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Playwright MCP, so you can run agents against it safely.

FAQ

Questions about browser_pdf_save

What does the browser_pdf_save tool do? +

browser_pdf_save. It is categorised as a Write tool in the Playwright MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on browser_pdf_save? +

Register the Playwright MCP server in PolicyLayer and add a rule for browser_pdf_save: 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 Playwright MCP. Nothing to install.

What risk level is browser_pdf_save? +

browser_pdf_save is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit browser_pdf_save? +

Yes. Add a rate_limit block to the browser_pdf_save 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.

How do I block browser_pdf_save completely? +

Set action: deny in the PolicyLayer policy for browser_pdf_save. 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.

What MCP server provides browser_pdf_save? +

browser_pdf_save is provided by the Playwright MCP server (lysander72/playwright-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.