execute_bof_pack
Execute a BOF with packing
This record as markdown: /tools/mickeydb-cobalt-strike-mcp/execute-bof-pack.md
What execute_bof_pack does on Cobalt Strike MCP Server
AI agents invoke execute_bof_pack 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_bof_pack is rated High
This tool executes arbitrary compiled code (BOF - Beacon Object File) on remote compromised systems via Cobalt Strike beacons. Execution of code is the most severe risk category applicable here. Packing suggests evasion/obfuscation of the code being run.
From the tool's definition Tool name 'execute_bof_pack' combined with server description stating '200+ tools for beacon control' and presence of sibling tools like 'beacon_upload_file' and 'beacon_download_file' confirms this is a Cobalt Strike command server.
Attacks that exploit this kind of access
The rule that runs execute_bof_pack 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 execute_bof_pack, this is the rule to start with:
execute_bof_pack 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Cobalt Strike MCP Server, apply this rule, and every execute_bof_pack call is checked against it from then on.
Questions about execute_bof_pack
Execute a BOF with packing. 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.
Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for execute_bof_pack: 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.
execute_bof_pack is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_bof_pack 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.
Set action: deny in the PolicyLayer policy for execute_bof_pack. 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.
execute_bof_pack 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.
Across the catalogue