High Risk →

puppeteer_pdf

Generate PDF from the current page

How to control puppeteer_pdf ↓

What puppeteer_pdf does on Claude TypeScript MCP Servers

AI agents invoke puppeteer_pdf to trigger actions in Claude TypeScript MCP Servers. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Why puppeteer_pdf needs a policy

This tool triggers a browser action (PDF generation from the current page state), which is an Execute-category operation. It runs an external operation (puppeteer browser automation) whose effects depend on the current page context.

From the tool's definition Generate PDF from the current page

Documented attack patterns abuse exactly the kind of access puppeteer_pdf gives an agent:

How to control puppeteer_pdf

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude TypeScript MCP Servers, and nothing reaches the server without passing your rules. This is the rule we recommend for puppeteer_pdf:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "puppeteer_pdf": {
      "limits": [
        {
          "counter": "puppeteer_pdf_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

puppeteer_pdf stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Claude TypeScript MCP Servers — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about puppeteer_pdf

What does the puppeteer_pdf tool do? +

Generate PDF from the current page. It is categorised as a Execute tool in the Claude TypeScript MCP Servers MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on puppeteer_pdf? +

Register the Claude TypeScript MCP Servers MCP server in PolicyLayer and add a rule for puppeteer_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 Claude TypeScript MCP Servers. Nothing to install.

What risk level is puppeteer_pdf? +

puppeteer_pdf is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit puppeteer_pdf? +

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

How do I block puppeteer_pdf completely? +

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

What MCP server provides puppeteer_pdf? +

puppeteer_pdf is provided by the Claude TypeScript MCP Servers MCP server (ukkz/claude-ts-mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude TypeScript MCP Servers tool call.

Start from Claude TypeScript MCP Servers, 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.

84 Claude TypeScript MCP Servers tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.