execute_get_system · Cobalt Strike MCP Server MCP

WHAT IT DOES

What execute_get_system does on Cobalt Strike MCP Server

AI agents invoke execute_get_system 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 execute_get_system needs a policy

This tool executes a privilege escalation attack to obtain SYSTEM (highest Windows privilege level), enabling unrestricted control of the target system. While privilege escalation itself is an Execute action (triggers external OS operations), the critical severity reflects that successful execution grants complete system compromise.

From the tool's definition Tool name is 'execute_get_system' with description 'Get SYSTEM privileges'. The execute_ prefix combined with privilege escalation to SYSTEM level indicates code execution that triggers external OS operations with severe security implications.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_get_system Rate-limited

execute_get_system 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": {
    "execute_get_system": {
      "limits": [
        {
          "counter": "execute_get_system_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 execute_get_system

What does the execute_get_system tool do? +

Get SYSTEM 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 execute_get_system? +

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

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

Can I rate-limit execute_get_system? +

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

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

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