powershell_encoded
Run local PowerShell using -EncodedCommand with UTF-16LE base64.
This record as markdown: /tools/mcp-control-plane/powershell-encoded.md
What powershell_encoded does on Mcp Control Plane
AI agents invoke powershell_encoded to trigger actions in Mcp Control Plane. 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 powershell_encoded is rated High
powershell_encoded invokes a shell interpreter with the ability to run arbitrary PowerShell scripts and commands. Encoding via base64 is a common obfuscation mechanism but does not change the underlying capability: executing system commands with full access to the host. An AI agent could use this to execute malicious scripts, access sensitive system resources, modify files, or establish persistence.
From the tool's definition Tool executes local PowerShell commands via -EncodedCommand with base64-encoded UTF-16LE input. This allows arbitrary code execution on the host system.
Attacks that exploit this kind of access
The rule that runs powershell_encoded safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For powershell_encoded, this is the rule to start with:
powershell_encoded 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every powershell_encoded call is checked against it from then on.
Questions about powershell_encoded
Run local PowerShell using -EncodedCommand with UTF-16LE base64. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for powershell_encoded: 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 Mcp Control Plane. Nothing to install.
powershell_encoded 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 powershell_encoded 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 powershell_encoded. 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.
powershell_encoded is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
Across the catalogue