execute_make_token_upn · Cobalt Strike MCP Server MCP

WHAT IT DOES

What execute_make_token_upn does on Cobalt Strike MCP Server

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

This tool creates authentication tokens using User Principal Names, which is a credential operation within an offensive security framework. Token creation is an Execute action—it performs operations whose effects depend on arguments (which UPN is targeted). The blast radius is critical: a compromised agent could create unauthorized tokens to impersonate users, escalate privileges, or maintain persistence.

From the tool's definition Tool named 'execute_make_token_upn' with description 'Make a token using UPN (User Principal Name)'. The 'execute' prefix and action of creating security tokens indicates this triggers external operations with significant security implications.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_make_token_upn Rate-limited

execute_make_token_upn 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_make_token_upn": {
      "limits": [
        {
          "counter": "execute_make_token_upn_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_make_token_upn

What does the execute_make_token_upn tool do? +

Make a token using UPN (User Principal Name). 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_make_token_upn? +

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

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

Can I rate-limit execute_make_token_upn? +

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

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

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