Low Risk

puppeteer_get_cookies

Get all cookies for the current page

How to control puppeteer_get_cookies ↓

What puppeteer_get_cookies does on Claude TypeScript MCP Servers

AI agents call puppeteer_get_cookies to retrieve information from Claude TypeScript MCP Servers without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why puppeteer_get_cookies needs a policy

This tool retrieves cookie information from the browser's current page. It performs a read-only query operation that does not modify, delete, or execute any actions. While cookies may contain sensitive session tokens, the tool itself only reads and returns data without side effects.

From the tool's definition Tool name 'puppeteer_get_cookies' and description 'Get all cookies for the current page' indicate retrieval of existing data with no modification or side effects.

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

How to control puppeteer_get_cookies

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_get_cookies:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "puppeteer_get_cookies": {}
  }
}

puppeteer_get_cookies is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about puppeteer_get_cookies

What does the puppeteer_get_cookies tool do? +

Get all cookies for the current page. It is categorised as a Read tool in the Claude TypeScript MCP Servers MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on puppeteer_get_cookies? +

Register the Claude TypeScript MCP Servers MCP server in PolicyLayer and add a rule for puppeteer_get_cookies: 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_get_cookies? +

puppeteer_get_cookies is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit puppeteer_get_cookies? +

Yes. Add a rate_limit block to the puppeteer_get_cookies 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_get_cookies completely? +

Set action: deny in the PolicyLayer policy for puppeteer_get_cookies. 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_get_cookies? +

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