convert_powershell
AI agents invoke convert_powershell to trigger actions in SousChef. 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.
The tool name suggests conversion of PowerShell code, likely transforming PowerShell scripts or resources into Ansible equivalents. In the context of a migration tool suite, this likely involves parsing and executing or generating executable code artifacts. However, the description is empty so confidence is lowered.
From the tool's definition Tool name 'convert_powershell' combined with server context mentioning 'analyze_powershell_fidelity' sibling tool and Chef-to-Ansible migration. Description is empty/uninformative.
Documented attack patterns abuse exactly the kind of access convert_powershell gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SousChef, and nothing reaches the server without passing your rules. This is the rule we recommend for convert_powershell:
{
"version": "1",
"default": "deny",
"tools": {
"convert_powershell": {
"limits": [
{
"counter": "convert_powershell_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}convert_powershell 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.
Free to start. No card required.
convert_powershell. It is categorised as a Execute tool in the SousChef MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SousChef MCP server in PolicyLayer and add a rule for convert_powershell: 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 SousChef. Nothing to install.
convert_powershell 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 convert_powershell 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 convert_powershell. 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.
convert_powershell is provided by the SousChef MCP server (kpeacocke/souschef). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SousChef, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
96 SousChef tools catalogued and risk-classified — across an index of 43,000+ MCP servers.