browser_cookie_list
AI agents call browser_cookie_list 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 'list' suffix and context of cookie management operations indicate this tool retrieves and enumerates cookie data. Listing cookies has no side effects and poses minimal security risk compared to setting or deleting cookies. While the empty description reduces confidence slightly, the naming convention and functional context of similar tools on the server strongly suggest read-only behavior.
From the tool's definition Tool name 'browser_cookie_list' indicates a listing/query operation. No description provided, but the naming pattern (list suffix) and sibling tools (browser_cookie_get, browser_cookie_set, browser_cookie_delete) suggest this retrieves cookie data without…
Attacks that exploit this kind of access
browser_cookie_list. 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_list: 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_list 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_list 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_list. 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_list is provided by the Playwright MCP server (naumana3services-maker/mcp). 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 →