execute_browserpivot_stop
Stop browser pivot
This record as markdown: /tools/mickeydb-cobalt-strike-mcp/execute-browserpivot-stop.md
What execute_browserpivot_stop does on Cobalt Strike MCP Server
AI agents invoke execute_browserpivot_stop to trigger actions in Cobalt Strike MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why execute_browserpivot_stop is rated High
Stopping a browser pivot terminates an active exploitation channel on a compromised system. While not destructive or financial, this is an Execute action because it triggers termination of an external operation whose effects depend on the target state.
From the tool's definition Tool is part of a Cobalt Strike red team operations server ("beacon control") that manages active compromises.
Attacks that exploit this kind of access
The rule that runs execute_browserpivot_stop safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cobalt Strike MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For execute_browserpivot_stop, this is the rule to start with:
execute_browserpivot_stop stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cobalt Strike MCP Server, apply this rule, and every execute_browserpivot_stop call is checked against it from then on.
Questions about execute_browserpivot_stop
Stop browser pivot. It is categorised as a Execute tool in the Cobalt Strike MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for execute_browserpivot_stop: 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 Cobalt Strike MCP Server. Nothing to install.
execute_browserpivot_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_browserpivot_stop 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 execute_browserpivot_stop. 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.
execute_browserpivot_stop is provided by the Cobalt Strike MCP Server MCP server (mickeydb/cobalt-strike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cobalt Strike MCP Server, and thousands of servers like it.
Across the catalogue