AI agents call rollback_v2_migration to permanently remove resources in SousChef — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name suggests rolling back a v2 migration, which typically involves undoing changes made during a migration process. Rollback operations can be destructive as they may overwrite or delete data/configuration created during the migration. However, the description is empty, which significantly lowers confidence.
From the tool's definition Tool name 'rollback_v2_migration' implies reverting or undoing a migration, which could irreversibly alter infrastructure state.
Documented attack patterns abuse exactly the kind of access rollback_v2_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 rollback_v2_migration:
{
"version": "1",
"default": "deny",
"hide": [
"rollback_v2_migration"
]
}rollback_v2_migration disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
rollback_v2_migration. It is categorised as a Destructive tool in the SousChef MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SousChef MCP server in PolicyLayer and add a rule for rollback_v2_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.
rollback_v2_migration is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the rollback_v2_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 rollback_v2_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.
rollback_v2_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.