browser_cookie_get
AI agents call browser_cookie_get to retrieve information from Playwright MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' suffix and its position among other cookie management tools (cookie_list, cookie_set, cookie_delete, cookie_clear) indicates this retrieves cookie values. Reading cookies has no destructive or executable effects—it only accesses existing browser state data. This is the least severe category.
From the tool's definition Tool name is 'browser_cookie_get' which indicates retrieval of cookie data. The description is empty, but the naming convention and context within a browser automation suite strongly suggest this is a read operation that retrieves existing cookies without…
Attacks that exploit this kind of access
browser_cookie_get. It is categorised as a Read tool in the Playwright MCP MCP Server, which means it retrieves data without modifying state.
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.
browser_cookie_get 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_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.
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.
browser_cookie_get is provided by the Playwright MCP server (roshan571/playwright-mcp2). 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 →