crow_browser_add_cookies

Inject cookies into the current context (e.g. a copied session). Each cookie needs name, value, and either url or domain+path.

SERVERCrow SOURCEkh0pper/crow

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/kh0pper-crow/crow-browser-add-cookies.md

WHAT IT DOES

What crow_browser_add_cookies does on Crow

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

RISK

Why crow_browser_add_cookies is rated Medium

The tool injects (creates/modifies) cookies, which are reversible state changes. This is a Write action rather than Execute because it doesn't run arbitrary code or trigger external operations — it manipulates stored credentials/session data.

From the tool's definition Tool description states 'Inject cookies into the current context' and requires 'name, value, and either url or domain+path' — this creates/modifies browser state by adding cookies.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crow_browser_add_cookies safely

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

crow_browser_add_cookies Rate-limited

crow_browser_add_cookies 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": {
    "crow_browser_add_cookies": {
      "limits": [
        {
          "counter": "crow_browser_add_cookies_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 Crow, apply this rule, and every crow_browser_add_cookies call is checked against it from then on.

FAQ

Questions about crow_browser_add_cookies

What does the crow_browser_add_cookies tool do? +

Inject cookies into the current context (e.g. a copied session). Each cookie needs name, value, and either url or domain+path. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on crow_browser_add_cookies? +

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

What risk level is crow_browser_add_cookies? +

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

Can I rate-limit crow_browser_add_cookies? +

Yes. Add a rate_limit block to the crow_browser_add_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 crow_browser_add_cookies completely? +

Set action: deny in the PolicyLayer policy for crow_browser_add_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 crow_browser_add_cookies? +

crow_browser_add_cookies is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb →add_video on Mcptube Vision → The MCP Attack Database →

Guides

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