convert_salt_pillar_to_vars
AI agents use convert_salt_pillar_to_vars 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 tool appears to transform configuration data from Salt format to Ansible format, which is a reversible data conversion/creation operation typical of migration tools. This falls under Write (creates or modifies data reversibly) rather than Read (no side effects) because it generates new Ansible variable representations.
From the tool's definition Tool name 'convert_salt_pillar_to_vars' indicates transformation of Salt pillar data into Ansible variables. The 'convert' prefix suggests creating or modifying data structures. Description is empty, limiting confidence.
Documented attack patterns abuse exactly the kind of access convert_salt_pillar_to_vars 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_salt_pillar_to_vars:
{
"version": "1",
"default": "deny",
"tools": {
"convert_salt_pillar_to_vars": {
"limits": [
{
"counter": "convert_salt_pillar_to_vars_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}convert_salt_pillar_to_vars 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_salt_pillar_to_vars. 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_salt_pillar_to_vars: 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_salt_pillar_to_vars 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_salt_pillar_to_vars 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_salt_pillar_to_vars. 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_salt_pillar_to_vars 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.