Check what browser data is accessible. Useful for debugging.
AI agents call check_sync_status 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 metadata or status information about what browser data is currently accessible. It has no side effects—it only queries and reports the sync status and available data categories. It is clearly a Read operation.
From the tool's definition Tool named 'check_sync_status' with description 'Check what browser data is accessible.' Returns information about accessible browser data (tabs, history, bookmarks) from local Chromium profiles without requiring authentication.
Attacks that exploit this kind of access
Check what browser data is accessible. Useful for debugging. 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 check_sync_status: 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.
check_sync_status 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 check_sync_status 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 check_sync_status. 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.
check_sync_status 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 →