set_beacon_c2_failover_notification
Enable or disable C2 failover notification
This record as markdown: /tools/mickeydb-cobalt-strike-mcp/set-beacon-c2-failover-notification.md
What set_beacon_c2_failover_notification does on Cobalt Strike MCP Server
AI agents use set_beacon_c2_failover_notification to create or update resources in Cobalt Strike MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cobalt Strike MCP Server environment.
Why set_beacon_c2_failover_notification is rated Medium
This tool modifies the configuration state of a C2 (command-and-control) beacon by toggling failover notifications on or off. It's a reversible configuration change (Write), but the context is a Cobalt Strike red team operation server, meaning misconfiguration could affect the reliability and stealthiness of active red team (or malicious) C2 infrastructure.
From the tool's definition Enable or disable C2 failover notification
Attacks that exploit this kind of access
The rule that runs set_beacon_c2_failover_notification 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_c2_failover_notification, this is the rule to start with:
set_beacon_c2_failover_notification stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 set_beacon_c2_failover_notification call is checked against it from then on.
Questions about set_beacon_c2_failover_notification
Enable or disable C2 failover notification. It is categorised as a Write tool in the Cobalt Strike MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for set_beacon_c2_failover_notification: 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.
set_beacon_c2_failover_notification is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_beacon_c2_failover_notification 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 set_beacon_c2_failover_notification. 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.
set_beacon_c2_failover_notification 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.
This server
Across the catalogue