chrome_bookmark_add · Chrome MCP Server MCP: Risk & Policy

WHAT IT DOES

What chrome_bookmark_add does on Chrome MCP Server

AI agents use chrome_bookmark_add to create or update resources in Chrome MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Chrome MCP Server environment.

WHY IT NEEDS A POLICY

Why chrome_bookmark_add needs a policy

Adding bookmarks creates or modifies browser state (the bookmark collection) but does not execute code, access sensitive data with read-like intent, delete data, or commit financial transactions. It is a standard Write operation with low severity since bookmarks are user preference data with minimal blast radius if misused by an AI agent—worst case being unwanted bookmarks added to the user's collection.

From the tool's definition Tool name 'chrome_bookmark_add' and description 'Add new bookmarks with folder support' indicate creation of new bookmark entries, a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chrome_bookmark_add Rate-limited

chrome_bookmark_add stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "chrome_bookmark_add": {
      "limits": [
        {
          "counter": "chrome_bookmark_add_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Chrome MCP Server, so you can run agents against it safely.

FAQ

Questions about chrome_bookmark_add

What does the chrome_bookmark_add tool do? +

Add new bookmarks with folder support. It is categorised as a Write tool in the Chrome MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on chrome_bookmark_add? +

Register the Chrome MCP Server MCP server in PolicyLayer and add a rule for chrome_bookmark_add: 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 Chrome MCP Server. Nothing to install.

What risk level is chrome_bookmark_add? +

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

Can I rate-limit chrome_bookmark_add? +

Yes. Add a rate_limit block to the chrome_bookmark_add 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 chrome_bookmark_add completely? +

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

chrome_bookmark_add is provided by the Chrome MCP Server MCP server (mnisred/mcp-chrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.