browser_cookie_get

A read tool on the Playwright MCP server.

SERVERPlaywright MCP SOURCEalialobidm/playwright-mcp

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/alialobidm-playwright-mcp/browser-cookie-get.md

WHAT IT DOES

What browser_cookie_get does on Playwright MCP

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

RISK

Why browser_cookie_get is rated Low

The 'get' verb universally indicates data retrieval without modification. Retrieving cookies from a browser is a read operation with no side effects—it queries stored session or preference data. While cookies can contain sensitive information, the operation itself is non-destructive and non-reversible-modification.

From the tool's definition Tool name 'browser_cookie_get' indicates retrieval of cookie data; consistent with sibling tools like 'browser_cookie_list' which are read-only.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_cookie_get safely

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

browser_cookie_get Allowed

browser_cookie_get 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": {
    "browser_cookie_get": {}
  }
}

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

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

FAQ

Questions about browser_cookie_get

What does the browser_cookie_get tool do? +

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

How do I enforce a policy on browser_cookie_get? +

Register the Playwright MCP server in PolicyLayer and add a rule for browser_cookie_get: 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_cookie_get? +

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

Can I rate-limit browser_cookie_get? +

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

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

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

KEEP EXPLORING

More on Playwright, and thousands of servers like it.

This server

All 59 Playwright 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 →