set_beacon_c2_failover_notification

WHAT IT DOES

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 IT NEEDS A POLICY

Why set_beacon_c2_failover_notification needs a policy

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

Recommended rule Ready

Verdict

set_beacon_c2_failover_notification Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_beacon_c2_failover_notification": {
      "limits": [
        {
          "counter": "set_beacon_c2_failover_notification_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 set_beacon_c2_failover_notification

What does the set_beacon_c2_failover_notification tool do? +

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.

How do I enforce a policy on set_beacon_c2_failover_notification? +

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.

What risk level is set_beacon_c2_failover_notification? +

set_beacon_c2_failover_notification is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_beacon_c2_failover_notification? +

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.

How do I block set_beacon_c2_failover_notification completely? +

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.

What MCP server provides set_beacon_c2_failover_notification? +

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.