New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

execute_browserpivot_stop

Stop browser pivot

SERVERCobalt Strike MCP Server SOURCEmickeydb/cobalt-strike-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about execute_browserpivot_stop

What does the execute_browserpivot_stop tool do? +

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.

How do I enforce a policy on execute_browserpivot_stop? +

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.

What risk level is execute_browserpivot_stop? +

execute_browserpivot_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_browserpivot_stop? +

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.

How do I block execute_browserpivot_stop completely? +

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.

What MCP server provides execute_browserpivot_stop? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Cobalt Strike MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.