Low Risk

get_cookies

Get browser cookies for the current page. Optionally filter by name or domain.

Part of the Safari DevTools MCP server.

get_cookies is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE SAFARI DEVTOOLS MCP →

Free to start. No card required.

AI agents call get_cookies to retrieve information from Safari DevTools MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_cookies only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_cookies": {}
  }
}

See the full Safari DevTools MCP policy for all 53 tools.

Get this rule live on your own Safari DevTools MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SAFARI DEVTOOLS MCP →

View all 53 tools →

These attack patterns abuse exactly the kind of access get_cookies gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_cookies only ever does what you allow.

SECURE SAFARI DEVTOOLS MCP →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_cookies tool do? +

Get browser cookies for the current page. Optionally filter by name or domain.. It is categorised as a Read tool in the Safari DevTools MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_cookies? +

Register the Safari DevTools 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 Safari DevTools MCP. Nothing to install.

What risk level is get_cookies? +

get_cookies is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_cookies? +

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.

How do I block get_cookies completely? +

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.

What MCP server provides get_cookies? +

get_cookies is provided by the Safari DevTools MCP server (safari-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Safari DevTools MCP tool call.

Deterministic rules across all 53 Safari DevTools MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.