set_beacon_ppid

Set the parent process ID for a beacon

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

WHAT IT DOES

What set_beacon_ppid does on Cobalt Strike MCP Server

AI agents invoke set_beacon_ppid 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 set_beacon_ppid is rated High

Setting the PPID (parent process ID) for a beacon is an Execute-category action because it configures how the beacon spawns child processes, affecting active red team implant behavior. This is a significant offensive security capability that can be used to evade detection by spoofing legitimate parent processes.

From the tool's definition 'Set the parent process ID for a beacon' — modifies runtime execution context of a Cobalt Strike beacon by changing its parent process spoofing configuration

Attacks that exploit this kind of access

RECOMMENDED RULE

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

set_beacon_ppid Rate-limited

set_beacon_ppid 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": {
    "set_beacon_ppid": {
      "limits": [
        {
          "counter": "set_beacon_ppid_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 set_beacon_ppid call is checked against it from then on.

FAQ

Questions about set_beacon_ppid

What does the set_beacon_ppid tool do? +

Set the parent process ID for a beacon. 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 set_beacon_ppid? +

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

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

Can I rate-limit set_beacon_ppid? +

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

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

set_beacon_ppid 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

set_breakpoint on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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