execute_rev2self

What execute_rev2self does on Cobalt Strike MCP Server

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

This tool executes a security context modification command on a beacon (compromised host). While not destructive to data and not a read operation, it performs an active operation that changes the runtime state of the compromised system. The high severity reflects that in a multi-stage attack, token management is a critical capability for attackers to maintain control and escalate privileges.

From the tool's definition Tool name 'execute_rev2self' and description 'Revert to self (drop impersonated token)' indicate execution of a Windows security operation that modifies the beacon's current security context by terminating token impersonation.

The rule that runs execute_rev2self 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_rev2self, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_rev2self": {
      "limits": [
        {
          "counter": "execute_rev2self_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about execute_rev2self