manage_profiles

THE RISK

Medium Risk

Why manage_profiles needs a policy

This tool creates or modifies persistent browser profiles containing sensitive session data (cookies, logins, credentials). While reversible (profiles can be updated or replaced), it affects authentication state and session persistence across browser operations.

From the tool's definition Tool description states it manages browser profiles that 'persist cookies, logins, and session data across browser sessions.' The ability to create, modify, or update stored authentication credentials and session data constitutes reversible data modification.

Documented attack patterns abuse exactly the kind of access manage_profiles gives an agent:

POLICY

How to control manage_profiles

PolicyLayer is an MCP gateway — it sits between your AI agents and Kernel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_profiles:

policy.json

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

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

Create a free account and register Kernel MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Kernel MCP Server tools

Execute computer_action Execute computer actions on a browser session. Pass a single action for simple operations Execute exec_command Execute a command synchronously inside a browser VM. Returns stdout, stderr, and exit code Execute execute_playwright_code Execute Playwright/TypeScript automation code against a Kernel browser session. If session Execute browser_curl Send an HTTP request through an existing Kernel browser session Execute manage_apps Manage Kernel apps, deployments, and invocations. Use Execute manage_browser_pools Manage pools of pre-warmed browser instances for fast acquisition. Use Execute manage_browsers Manage browser sessions in the Kernel platform. Use action Write manage_api_keys Manage Kernel API keys. Use

All 16 Kernel MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about manage_profiles

What does the manage_profiles tool do? +

Manage browser profiles that persist cookies, logins, and session data across browser sessions. Use action. It is categorised as a Write tool in the Kernel 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 manage_profiles? +

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

What risk level is manage_profiles? +

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

Can I rate-limit manage_profiles? +

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

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

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

Enforce policy on every Kernel MCP Server tool call.

Start from Kernel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →