set_cookie

A write tool on the Chrome Devtools MCP server.

SERVERChrome Devtools SOURCEbenjaminr/chrome-devtools-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/benjaminr-chrome-devtools-mcp/set-cookie.md

WHAT IT DOES

What set_cookie does on Chrome Devtools

AI agents use set_cookie to create or update resources in Chrome Devtools, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Chrome Devtools environment.

RISK

Why set_cookie is rated Medium

Setting cookies is a reversible Write operation—it creates or modifies browser storage. While not destructive (cookies can be cleared), it has high severity because malicious cookie injection could enable session hijacking, credential theft, or tracking. The context of Chrome DevTools and presence of cookie-clearing functions confirms this is cookie manipulation.

From the tool's definition Tool name 'set_cookie' and sibling tool 'clear_all_cookies' in a Chrome DevTools context indicate cookie manipulation. The function sets cookies, which modifies browser state and stored data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_cookie safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_cookie, this is the rule to start with:

set_cookie Rate-limited

set_cookie 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_cookie": {
      "limits": [
        {
          "counter": "set_cookie_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every set_cookie call is checked against it from then on.

FAQ

Questions about set_cookie

What does the set_cookie tool do? +

set_cookie is a write tool on the Chrome Devtools MCP server. It is categorised as a Write tool in the Chrome Devtools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_cookie? +

Register the Chrome Devtools MCP server in PolicyLayer and add a rule for set_cookie: 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 Chrome Devtools. Nothing to install.

What risk level is set_cookie? +

set_cookie is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_cookie? +

Yes. Add a rate_limit block to the set_cookie 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.

How do I block set_cookie completely? +

Set action: deny in the PolicyLayer policy for set_cookie. 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.

What MCP server provides set_cookie? +

set_cookie is provided by the Chrome Devtools MCP server (benjaminr/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome Devtools, and thousands of servers like it.

This server

All 47 Chrome Devtools tools →

Across the catalogue

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →