execute_bof_packed · Cobalt Strike MCP Server MCP

WHAT IT DOES

What execute_bof_packed does on Cobalt Strike MCP Server

AI agents invoke execute_bof_packed 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 execute_bof_packed needs a policy

This tool executes arbitrary compiled code (BOF) on remote compromised systems, with effects determined entirely by the BOF's contents. This is a core Execute capability: triggering external operations whose outcomes depend on arguments.

From the tool's definition Tool name 'execute_bof_packed' directly indicates execution of a BOF (Beacon Object File). BOFs are compiled code objects executed on compromised hosts within Cobalt Strike operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_bof_packed Rate-limited

execute_bof_packed 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": {
    "execute_bof_packed": {
      "limits": [
        {
          "counter": "execute_bof_packed_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 execute_bof_packed

What does the execute_bof_packed tool do? +

Execute a packed BOF. 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_bof_packed? +

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

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

Can I rate-limit execute_bof_packed? +

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

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

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