set_profile_path · Chromium Sync MCP: Risk & Policy

WHAT IT DOES

What set_profile_path does on Chromium Sync

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

WHY IT NEEDS A POLICY

Why set_profile_path needs a policy

This tool modifies configuration settings (the profile path variable) in a reversible manner. While it doesn't create/delete data directly, it changes which browser profile the MCP server will access, which could redirect data queries to a different user context. This is a Write operation because it updates stored configuration.

From the tool's definition Tool name is 'set_profile_path' and description states it will 'Manually set the browser profile path.' This modifies configuration state that directs where the server reads browser data from.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_profile_path Rate-limited

set_profile_path 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": {
    "set_profile_path": {
      "limits": [
        {
          "counter": "set_profile_path_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 Chromium Sync, so you can run agents against it safely.

FAQ

Questions about set_profile_path

What does the set_profile_path tool do? +

Manually set the browser profile path. It is categorised as a Write tool in the Chromium Sync MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_profile_path? +

Register the Chromium Sync MCP server in PolicyLayer and add a rule for set_profile_path: 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.

What risk level is set_profile_path? +

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

Can I rate-limit set_profile_path? +

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

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

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