Execute unmanaged PowerShell
AI agents invoke inject_powershell_unmanaged 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.
This tool executes code (PowerShell) directly via injection, which is an Execute category action. The severity is critical because: (1) arbitrary PowerShell execution grants near-complete system control; (2) 'unmanaged' bypasses defensive mechanisms; (3) Cobalt Strike is a red team framework designed for adversarial operations; (4) blast radius includes credential theft, lateral movement, persistence, and data…
From the tool's definition Tool name 'inject_powershell_unmanaged' and description 'Execute unmanaged PowerShell' explicitly indicate execution of arbitrary PowerShell code. 'Unmanaged' execution bypasses security constraints and allows direct code injection.
Attacks that exploit this kind of access
Execute unmanaged PowerShell. 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.
Register the Cobalt Strike MCP Server MCP server in PolicyLayer and add a rule for inject_powershell_unmanaged: 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.
inject_powershell_unmanaged is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the inject_powershell_unmanaged 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.
Set action: deny in the PolicyLayer policy for inject_powershell_unmanaged. 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.
inject_powershell_unmanaged 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →