execute_get_uid · Cobalt Strike MCP Server MCP

WHAT IT DOES

What execute_get_uid does on Cobalt Strike MCP Server

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

This tool executes commands on remote targets (get user ID is a system command execution), which falls under Execute category. Severity is high because it enables reconnaissance on compromised systems that could inform further attacks, and the broader server context shows this is part of red team offensive operations with destructive capabilities (beacon_delete_file, beacon_move_file).

From the tool's definition Tool is part of Cobalt Strike red team operations server with 200+ beacon control tools. 'execute_get_uid' executes a command to retrieve user ID on a compromised target system, consistent with post-exploitation reconnaissance activities alongside…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_get_uid Rate-limited

execute_get_uid 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_uid": {
      "limits": [
        {
          "counter": "execute_get_uid_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_uid

What does the execute_get_uid tool do? +

Get user ID. 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_uid? +

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

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

Can I rate-limit execute_get_uid? +

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

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

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