Get cookies from the current browser context.
AI agents call browser.get_cookies to retrieve information from MCP Playwright Browser without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves existing cookie data from the browser context. It performs no write, execute, destructive, or financial operations. The blast radius of misuse is minimal—an attacker could learn about stored cookies but cannot modify them or access data beyond what the browser already knows. Classification as Read is appropriate.
From the tool's definition Tool name is 'browser.get_cookies' and description states 'Get cookies from the current browser context' — purely retrieves data with no modification or side effects.
Attacks that exploit this kind of access
Get cookies from the current browser context. It is categorised as a Read tool in the MCP Playwright Browser MCP Server, which means it retrieves data without modifying state.
Register the MCP Playwright Browser MCP server in PolicyLayer and add a rule for browser.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 MCP Playwright Browser. Nothing to install.
browser.get_cookies is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the browser.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.
Set action: deny in the PolicyLayer policy for browser.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.
browser.get_cookies is provided by the MCP Playwright Browser MCP server (mhrnqaruni/mcp-playwright-browser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →