browser_get_cookies
A read tool on the Looking Glass MCP server.
This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/browser-get-cookies.md
What browser_get_cookies does on Looking Glass
AI agents call browser_get_cookies to retrieve information from Looking Glass without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | — | Filter cookies by URL |
Parameters from the server's own tool schema.
Why browser_get_cookies is rated Low
Cookie retrieval is a read-only operation that queries stored browser state without modification or deletion. While cookies can contain sensitive data (session tokens, auth credentials), the tool itself performs no destructive or state-altering action.
From the tool's definition Tool name 'browser_get_cookies' indicates retrieval of cookie data; 'get' is a read operation pattern. The tool description is empty, but the name and context (AI-native browser) strongly suggest data retrieval with no side effects.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs browser_get_cookies safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Looking Glass, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_get_cookies, this is the rule to start with:
browser_get_cookies is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Looking Glass, apply this rule, and every browser_get_cookies call is checked against it from then on.
Questions about browser_get_cookies
browser_get_cookies is a read tool on the Looking Glass MCP server. It is categorised as a Read tool in the Looking Glass MCP Server, which means it retrieves data without modifying state.
browser_get_cookies accepts 1 parameter: url. The full parameter table on this page comes from the server's own tool schema.
Register the Looking Glass MCP server in PolicyLayer and add a rule for browser_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 Looking Glass. Nothing to install.
browser_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 browser_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 browser_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.
browser_get_cookies is provided by the Looking Glass MCP server (looking-glass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Looking Glass, and thousands of servers like it.
This server
Across the catalogue