Get bookmarks. Optionally filter by parent folder ID.
AI agents call get_bookmarks to retrieve information from Chromium Sync without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves bookmark data from the local browser profile without side effects. It is categorized as Read. Severity is medium because bookmarks may contain sensitive URLs (banking sites, private services, internal tools) that could inform reconnaissance or social engineering, but the tool itself does not modify or exfiltrate data—it only queries what is already available locally to the agent.
From the tool's definition Tool name is 'get_bookmarks' and description states 'Get bookmarks' with optional filtering—a data retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
Get bookmarks. Optionally filter by parent folder ID. It is categorised as a Read tool in the Chromium Sync MCP Server, which means it retrieves data without modifying state.
Register the Chromium Sync MCP server in PolicyLayer and add a rule for get_bookmarks: 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 Sync. Nothing to install.
get_bookmarks 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_bookmarks 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_bookmarks. 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_bookmarks is provided by the Chromium Sync MCP server (jaidhyani/chromium-sync-mcp). 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 →