inject_powershell_unmanaged

Execute unmanaged PowerShell

Server Cobalt Strike MCP Server mickeydb/cobalt-strike-mcp
Category Execute
Risk class High
Parameters 00 required

What inject_powershell_unmanaged does on Cobalt Strike MCP Server

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.

Why inject_powershell_unmanaged needs a policy

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.

Questions about inject_powershell_unmanaged

What does the inject_powershell_unmanaged tool do? +

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.

How do I enforce a policy on inject_powershell_unmanaged? +

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.

What risk level is inject_powershell_unmanaged? +

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

Can I rate-limit inject_powershell_unmanaged? +

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.

How do I block inject_powershell_unmanaged completely? +

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.

What MCP server provides inject_powershell_unmanaged? +

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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.