AI agents use browser_cookie_set to create or update resources in Playwright — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Playwright environment.
This tool creates or modifies cookies, which are reversible write operations. While cookies can be deleted, setting them modifies browser state and could enable session hijacking, credential theft, or tracking. It is more severe than a pure read operation but less severe than destructive deletion or financial transactions.
From the tool's definition Tool name 'browser_cookie_set' indicates it modifies browser cookies. Sibling tools like 'browser_cookie_delete' and 'browser_cookie_get' confirm this server operates on browser state. The '_set' suffix indicates data modification.
Documented attack patterns abuse exactly the kind of access browser_cookie_set gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_cookie_set:
{
"version": "1",
"default": "deny",
"tools": {
"browser_cookie_set": {
"limits": [
{
"counter": "browser_cookie_set_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
browser_cookie_set. It is categorised as a Write tool in the Playwright 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. 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 (@playwright/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
68 Playwright tools catalogued and risk-classified — across an index of 43,000+ MCP servers.