Set cookies in the current browser context.
AI agents use browser.set_cookies to create or update resources in MCP Playwright Browser — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Playwright Browser environment.
This tool modifies browser cookies, which are reversible session/authentication data. It creates or updates cookies without deleting them permanently, placing it in the Write category rather than Destructive.
From the tool's definition Tool name is 'browser.set_cookies' and description states 'Set cookies in the current browser context.' The verb 'set' indicates modification of browser state.
Attacks that exploit this kind of access
Set cookies in the current browser context. It is categorised as a Write tool in the MCP Playwright Browser MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Playwright Browser MCP server in PolicyLayer and add a rule for browser.set_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.set_cookies 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.set_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.set_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.set_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 →