Export all cookies from the current browser session as a JSON array (round-trips with set_cookies).
AI agents call get_cookies to retrieve information from Chromium ARM64 Browser without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is fundamentally a read operation—it retrieves data without modifying or deleting it. However, severity is high rather than low because cookies frequently contain sensitive credentials (session tokens, API keys, auth tokens) that could enable account takeover or unauthorized access if exposed to an attacker or malicious agent.
From the tool's definition Tool exports cookies from the browser session as a JSON array. Cookies often contain sensitive authentication tokens, session identifiers, and user tracking data.
Attacks that exploit this kind of access
Export all cookies from the current browser session as a JSON array (round-trips with set_cookies). It is categorised as a Read tool in the Chromium ARM64 Browser MCP Server, which means it retrieves data without modifying state.
Register the Chromium ARM64 Browser MCP server in PolicyLayer and add a rule for get_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 Chromium ARM64 Browser. Nothing to install.
get_cookies is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_cookies is provided by the Chromium ARM64 Browser MCP server (nfodor/mcp-chromium-arm64). 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 →