Manage browser extensions uploaded to your organization. Use
AI agents use manage_extensions to create or update resources in Kernel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kernel MCP Server environment.
Managing extensions for an organization involves creating, modifying, or updating extension configurations and metadata—reversible write operations. The severity is high because malicious extension management could inject malicious code into all browsers using those extensions, affecting multiple users and systems.
From the tool's definition Tool name is 'manage_extensions' and description states 'Manage browser extensions uploaded to your organization.' The verb 'manage' combined with 'uploaded' indicates create, modify, or update operations on browser extensions.
Documented attack patterns abuse exactly the kind of access manage_extensions gives an agent:
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_extensions:
{
"version": "1",
"default": "deny",
"tools": {
"manage_extensions": {
"limits": [
{
"counter": "manage_extensions_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_extensions 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.
Free to start. No card required.
Manage browser extensions uploaded to your organization. Use. 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.
Register the Kernel MCP Server MCP server in PolicyLayer and add a rule for manage_extensions: 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.
manage_extensions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the manage_extensions 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 manage_extensions. 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.
manage_extensions 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.
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.
Free to start. No card required.
16 Kernel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.