inject_browserpivotStart · Cobalt Strike MCP Server MCP

WHAT IT DOES

What inject_browserpivotStart does on Cobalt Strike MCP Server

AI agents invoke inject_browserpivotStart 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 IT NEEDS A POLICY

Why inject_browserpivotStart needs a policy

Browser pivot injection executes code within a target process (browser) to establish a foothold for further attacks, lateral movement, and command execution. This is a remote code execution primitive with high blast radius—an AI agent invoking this could compromise user systems, establish persistence, or pivot to other hosts.

From the tool's definition Tool name 'inject_browserpivotStart' indicates injection and pivoting operations; server description explicitly mentions 'beacon control' and 'payload generation' for red team operations; browser pivot is a Cobalt Strike feature that executes arbitrary code…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

inject_browserpivotStart Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "inject_browserpivotStart": {
      "limits": [
        {
          "counter": "inject_browserpivotstart_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Cobalt Strike MCP Server, so you can run agents against it safely.

FAQ

Questions about inject_browserpivotStart

What does the inject_browserpivotStart tool do? +

Start 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 inject_browserpivotStart? +

Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for inject_browserpivotStart: 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 inject_browserpivotStart? +

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

Can I rate-limit inject_browserpivotStart? +

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

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

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