Parse a Chef ERB template file and convert to Jinja2.
AI agents invoke parse_template 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.
This tool reads a file and transforms/converts it from one template format (ERB) to another (Jinja2). While it has a read component, the conversion and output generation constitute active processing with side effects (producing new content). It falls under Execute as it runs a transformation operation on files, though it could also be considered Write if it saves output.
From the tool's definition Parse a Chef ERB template file and convert to Jinja2
Documented attack patterns abuse exactly the kind of access parse_template 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 parse_template:
{
"version": "1",
"default": "deny",
"tools": {
"parse_template": {
"limits": [
{
"counter": "parse_template_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}parse_template 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.
Parse a Chef ERB template file and convert to Jinja2. 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 parse_template: 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.
parse_template 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 parse_template 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 parse_template. 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.
parse_template 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.