plan_salt_migration
AI agents call plan_salt_migration as a supporting operation in SousChef workflows.
With no description available, we can only infer from the name. 'Plan' suggests a read/analysis operation that generates a migration plan without executing changes, most likely similar to sibling tools like 'assess_salt_migration_complexity' which appear to be analytical/read tools. However, confidence is low due to the empty description.
From the tool's definition Tool description is empty and uninformative; tool name 'plan_salt_migration' only suggests planning a Salt-to-Ansible migration.
Documented attack patterns abuse exactly the kind of access plan_salt_migration 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 plan_salt_migration:
{
"version": "1",
"default": "deny",
"tools": {
"plan_salt_migration": {
"limits": [
{
"counter": "plan_salt_migration_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}plan_salt_migration gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
plan_salt_migration. It is categorised as a Other tool in the SousChef MCP Server, which means it performs auxiliary operations.
Register the SousChef MCP server in PolicyLayer and add a rule for plan_salt_migration: 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.
plan_salt_migration is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the plan_salt_migration 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 plan_salt_migration. 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.
plan_salt_migration 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.