elevate_command · Cobalt Strike MCP Server MCP

WHAT IT DOES

What elevate_command does on Cobalt Strike MCP Server

AI agents invoke elevate_command 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 IT NEEDS A POLICY

Why elevate_command needs a policy

This tool executes commands with escalated privileges within a Cobalt Strike red team context. Privilege escalation on a beacon allows arbitrary code execution as a higher-privileged user (e.g., SYSTEM), dramatically expanding blast radius. It sits in a server explicitly designed for offensive operations with beacon control, making misuse catastrophic.

From the tool's definition 'Elevate a command with higher privileges' — runs commands with elevated/admin privileges on a compromised beacon host

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

elevate_command Rate-limited

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

View as policy code

policy.json

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

RATE-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 elevate_command

What does the elevate_command tool do? +

Elevate a command with higher privileges. 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 elevate_command? +

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

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

Can I rate-limit elevate_command? +

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

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

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