empire_shell · PowerShell Empire MCP Server MCP

WHAT IT DOES

What empire_shell does on PowerShell Empire MCP Server

AI agents invoke empire_shell to trigger actions in PowerShell Empire 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 empire_shell needs a policy

This tool enables execution of arbitrary code on remote systems through an Empire agent. The ability to run shell commands grants complete operational control over the target and can lead to data exfiltration, lateral movement, malware deployment, or system compromise. Combined with the Empire framework's post-exploitation context (managing agents, modules, credentials), this represents critical risk.

From the tool's definition "Execute shell commands on an Empire agent" - the tool directly runs arbitrary shell commands on compromised systems via the Empire post-exploitation framework.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

empire_shell Rate-limited

empire_shell 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": {
    "empire_shell": {
      "limits": [
        {
          "counter": "empire_shell_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 PowerShell Empire MCP Server, so you can run agents against it safely.

FAQ

Questions about empire_shell

What does the empire_shell tool do? +

Execute shell commands on an Empire agent. It is categorised as a Execute tool in the PowerShell Empire 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 empire_shell? +

Register the PowerShell Empire MCP Server MCP server in PolicyLayer and add a rule for empire_shell: 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 PowerShell Empire MCP Server. Nothing to install.

What risk level is empire_shell? +

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

Can I rate-limit empire_shell? +

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

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

empire_shell is provided by the PowerShell Empire MCP Server MCP server (schwarztim/sec-powershell-empire-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.