adds a cookie to the current browser session. The browser must be on a page from the cookie
AI agents use add_cookie to create or update resources in Mcp Selenium — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Selenium environment.
Adding a cookie modifies browser session data reversibly. While this could potentially be misused to set tracking cookies or malicious session tokens, it does not execute arbitrary code, delete data, move money, or cause irreversible harm. It falls squarely in the Write category (creates/modifies data reversibly).
From the tool's definition Tool name 'add_cookie' and description 'adds a cookie to the current browser session' clearly indicate modification of browser state data. This is a write operation that creates or modifies cookies.
Attacks that exploit this kind of access
adds a cookie to the current browser session. The browser must be on a page from the cookie. It is categorised as a Write tool in the Mcp Selenium MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Selenium MCP server in PolicyLayer and add a rule for add_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 Mcp Selenium. Nothing to install.
add_cookie 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 add_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.
Set action: deny in the PolicyLayer policy for add_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.
add_cookie is provided by the Mcp Selenium MCP server (@angiejones/mcp-selenium). 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 →