New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

set_beacon_c2_host_hold

Hold C2 host (prevent failover)

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-c2-host-hold.md

What set_beacon_c2_host_hold does on Cobalt Strike MCP Server

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

This tool modifies the operational behavior of a Cobalt Strike C2 (Command & Control) host by preventing failover. It is an operational control action that affects the red team infrastructure's communication channels. While it doesn't directly delete data or move money, it executes a configuration change on live C2 infrastructure that could impact ongoing operations significantly.

From the tool's definition Hold C2 host (prevent failover)

Questions about set_beacon_c2_host_hold

What does the set_beacon_c2_host_hold tool do? +

Hold C2 host (prevent failover). 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_c2_host_hold? +

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

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

Can I rate-limit set_beacon_c2_host_hold? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Cobalt Strike MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.