execute_powershell_import · Cobalt Strike MCP Server MCP

WHAT IT DOES

What execute_powershell_import does on Cobalt Strike MCP Server

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

Importing PowerShell modules allows arbitrary code execution with the privileges of the running beacon process on a target system. This is fundamentally an Execute action (runs code whose effects depend on which module is imported and what that module does). Within a Cobalt Strike context, this is a critical capability for post-exploitation.

From the tool's definition Tool enables 'Import PowerShell module' which executes PowerShell code; server description states '200+ tools for beacon control' indicating offensive security operations; context of Cobalt Strike (adversary simulation framework) with beacon control tools…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_powershell_import Rate-limited

execute_powershell_import 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_powershell_import": {
      "limits": [
        {
          "counter": "execute_powershell_import_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_powershell_import

What does the execute_powershell_import tool do? +

Import PowerShell module. 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_powershell_import? +

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

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

Can I rate-limit execute_powershell_import? +

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

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

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