get_all_cookies

Get all browser cookies. Returns: List of all cookies with details

SERVERChrome Devtools SOURCEbenjaminr/chrome-devtools-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/benjaminr-chrome-devtools-mcp/get-all-cookies.md

WHAT IT DOES

What get_all_cookies does on Chrome Devtools

AI agents call get_all_cookies to retrieve information from Chrome Devtools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_all_cookies is rated Low

This tool retrieves and queries cookie data from the browser without modifying, deleting, or executing anything. It is a read-only operation. Severity is medium rather than low because cookies often contain sensitive authentication tokens, session identifiers, or personal data that could be misused if exposed to an untrusted AI agent, but the tool itself performs no destructive or operational actions.

From the tool's definition Tool name is 'get_all_cookies' and description states 'Get all browser cookies' with 'Returns: List of all cookies with details'. This is a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_all_cookies 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 get_all_cookies, this is the rule to start with:

get_all_cookies Allowed

get_all_cookies is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_all_cookies": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_all_cookies

What does the get_all_cookies tool do? +

Get all browser cookies. Returns: List of all cookies with details. It is categorised as a Read tool in the Chrome Devtools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_all_cookies? +

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

What risk level is get_all_cookies? +

get_all_cookies is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_all_cookies? +

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

How do I block get_all_cookies completely? +

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

What MCP server provides get_all_cookies? +

get_all_cookies 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →