convert_template_with_ai
AI agents use convert_template_with_ai to create or update resources in SousChef — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SousChef environment.
The name suggests this tool transforms Chef templates to Ansible equivalents as part of the migration workflow. Template conversion creates or modifies configuration files (reversible changes), placing it in the Write category. Severity is medium because template errors could affect infrastructure deployment, but the changes are not destructive and can be reviewed/reverted.
From the tool's definition Tool name 'convert_template_with_ai' indicates it converts templates, which is a modification operation. The empty description limits confidence in assessing exact scope and constraints.
Documented attack patterns abuse exactly the kind of access convert_template_with_ai 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_template_with_ai:
{
"version": "1",
"default": "deny",
"tools": {
"convert_template_with_ai": {
"limits": [
{
"counter": "convert_template_with_ai_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}convert_template_with_ai stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
convert_template_with_ai. It is categorised as a Write tool in the SousChef MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SousChef MCP server in PolicyLayer and add a rule for convert_template_with_ai: 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_template_with_ai is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the convert_template_with_ai 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_template_with_ai. 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_template_with_ai 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.