New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

browser_set_cookie

A write tool on the Looking Glass MCP server.

SERVERLooking Glass SOURCElooking-glass-mcp
Medium RISK CLASS
Category Write
Parameters 42 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/browser-set-cookie.md

What browser_set_cookie does on Looking Glass

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

ParameterTypeRequiredDescription
name string Yes Cookie name
path string Cookie path (default: /)
value string Yes Cookie value
domain string Cookie domain

Parameters from the server's own tool schema.

Why browser_set_cookie is rated Medium

Setting cookies modifies client-side state that persists across browser sessions and can affect authentication, tracking, and application behavior. This is a reversible write operation (cookies can be deleted/modified later), not read-only. It does not delete data (not Destructive), execute arbitrary code (not Execute in the dangerous sense), or move money (not Financial).

From the tool's definition Tool name 'browser_set_cookie' indicates modification of browser cookies. The name contains 'set', a write operation. Description is empty, which reduces confidence.

Risk signalsAccepts file system path (path)

Questions about browser_set_cookie

What does the browser_set_cookie tool do? +

browser_set_cookie is a write tool on the Looking Glass MCP server. It is categorised as a Write tool in the Looking Glass MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does browser_set_cookie accept? +

browser_set_cookie accepts 4 parameters: name, path, value, domain. Required: name, value. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on browser_set_cookie? +

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

What risk level is browser_set_cookie? +

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

Can I rate-limit browser_set_cookie? +

Yes. Add a rate_limit block to the browser_set_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.

How do I block browser_set_cookie completely? +

Set action: deny in the PolicyLayer policy for browser_set_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.

What MCP server provides browser_set_cookie? +

browser_set_cookie 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Looking Glass's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.