browser_cookie_set
A write tool on the Playwright MCP server.
This record as markdown: /tools/alialobidm-playwright-mcp/browser-cookie-set.md
What browser_cookie_set does on Playwright MCP
AI agents use browser_cookie_set to create or update resources in Playwright MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Playwright MCP environment.
Why browser_cookie_set is rated Medium
Setting cookies is a reversible modification operation that affects browser state and can influence web application behavior, session management, and authentication. While not destructive (cookies can be cleared), it modifies data and could be exploited to hijack sessions, manipulate authentication state, or inject malicious session data. Severity is high due to potential for session/authentication abuse.
From the tool's definition Tool name 'browser_cookie_set' indicates it sets/modifies browser cookies. Sibling tools 'browser_cookie_delete', 'browser_cookie_get', 'browser_cookie_list' confirm a cookie management suite. The naming pattern shows this is a Write operation (create/modify).
Attacks that exploit this kind of access
The rule that runs browser_cookie_set 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_set, this is the rule to start with:
browser_cookie_set stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Playwright MCP, apply this rule, and every browser_cookie_set call is checked against it from then on.
Questions about browser_cookie_set
browser_cookie_set is a write tool on the Playwright MCP server. It is categorised as a Write tool in the Playwright MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Playwright MCP server in PolicyLayer and add a rule for browser_cookie_set: 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_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the browser_cookie_set 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_set. 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_set 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.
More on Playwright, and thousands of servers like it.
This server
Across the catalogue