inject_beacon

Inject beacon into a process

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/inject-beacon.md

WHAT IT DOES

What inject_beacon does on Cobalt Strike MCP Server

AI agents invoke inject_beacon 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.

RISK

Why inject_beacon is rated High

Process injection is a core offensive security technique that executes arbitrary code within another process's memory space. In the context of a Cobalt Strike red team server, this enables covert code execution, privilege escalation, and lateral movement.

From the tool's definition 'Inject beacon into a process' — this tool injects a Cobalt Strike beacon payload into a running process

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs inject_beacon 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 inject_beacon, this is the rule to start with:

inject_beacon Rate-limited

inject_beacon 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_beacon": {
      "limits": [
        {
          "counter": "inject_beacon_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cobalt Strike MCP Server, apply this rule, and every inject_beacon call is checked against it from then on.

FAQ

Questions about inject_beacon

What does the inject_beacon tool do? +

Inject beacon into a process. 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_beacon? +

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

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

Can I rate-limit inject_beacon? +

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

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

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

KEEP EXPLORING

More on Cobalt Strike MCP Server, and thousands of servers like it.

This server

All 220 Cobalt Strike MCP Server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →