Disconnects a specific browser extension by its ID
AI agents use skippr_disconnect_extension to create or update resources in Skippr Extension MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Skippr Extension MCP Server environment.
This tool modifies system state by disconnecting an extension, which is reversible (can be reconnected) but impacts the runtime configuration of the extension ecosystem. It doesn't execute code or delete data, but it does change the state of connected extensions.
From the tool's definition Disconnects a specific browser extension by its ID - modifies the connection state of a running extension, affecting system configuration.
Attacks that exploit this kind of access
Disconnects a specific browser extension by its ID. It is categorised as a Write tool in the Skippr Extension MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Skippr Extension MCP Server MCP server in PolicyLayer and add a rule for skippr_disconnect_extension: 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 Skippr Extension MCP Server. Nothing to install.
skippr_disconnect_extension 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 skippr_disconnect_extension 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 skippr_disconnect_extension. 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.
skippr_disconnect_extension is provided by the Skippr Extension MCP Server MCP server (skippr-hq/extension-mcp-server). 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 →