Gestiona cookies de la sesión.
AI agents use manage_cookies to create or update resources in MCP Selenium WebDriver — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Selenium WebDriver environment.
Managing cookies involves writing or modifying browser state data. While reversible (cookies can be cleared), this enables manipulation of session state and authentication tokens, which could be leveraged to perform unauthorized actions (e.g., session hijacking, credential injection, bypassing security mechanisms).
From the tool's definition Tool name 'manage_cookies' and description 'Gestiona cookies de la sesión' (Manages session cookies) indicates the ability to create, modify, or set cookie data in a browser session.
Attacks that exploit this kind of access
Gestiona cookies de la sesión. It is categorised as a Write tool in the MCP Selenium WebDriver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Selenium WebDriver MCP server in PolicyLayer and add a rule for manage_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 MCP Selenium WebDriver. Nothing to install.
manage_cookies 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 manage_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.
Set action: deny in the PolicyLayer policy for manage_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.
manage_cookies is provided by the MCP Selenium WebDriver MCP server (nixon-suarez/mcp-selenium-webdriver). 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 →