get_cookies

A read tool on the Playwright MCP server.

SERVERPlaywright MCP Server SOURCEalexrwilliam/playwright-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexrwilliam-playwright-mcp-server/get-cookies.md

WHAT IT DOES

What get_cookies does on Playwright MCP Server

AI agents call get_cookies to retrieve information from Playwright MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_cookies is rated Low

This tool retrieves cookie data from the browser without modifying or deleting it. Cookie retrieval is a read-only operation with no side effects. While cookies may contain sensitive data (session tokens, etc.), the tool itself performs passive data extraction. Severity is low because reading cookies does not directly modify state, execute code, or trigger external operations—it simply queries stored browser data.

From the tool's definition Tool named 'get_cookies' with no description; sibling tools include 'add_cookies', 'clear_cookies' suggesting cookie management operations. The 'get_' prefix indicates retrieval/query action.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_cookies safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Playwright MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_cookies, this is the rule to start with:

get_cookies Allowed

get_cookies is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_cookies": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Playwright MCP Server, apply this rule, and every get_cookies call is checked against it from then on.

FAQ

Questions about get_cookies

What does the get_cookies tool do? +

get_cookies is a read tool on the Playwright MCP Server MCP server. It is categorised as a Read tool in the Playwright MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_cookies? +

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

What risk level is get_cookies? +

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

Can I rate-limit get_cookies? +

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

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

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

KEEP EXPLORING

More on Playwright MCP Server, and thousands of servers like it.

This server

All 67 Playwright MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →