Low Risk

list_migration_version_combinations

list_migration_version_combinations

How to control list_migration_version_combinations ↓

What list_migration_version_combinations does on SousChef

AI agents call list_migration_version_combinations to retrieve information from SousChef without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_migration_version_combinations needs a policy

The 'list_' prefix strongly indicates a query/retrieval operation that enumerates available version combinations for Chef-to-Ansible migration planning. No modification, deletion, execution, or financial transaction is implied. In the context of a migration analysis server, this tool likely returns metadata about compatible versions without side effects.

From the tool's definition Tool name 'list_migration_version_combinations' contains the verb 'list', which is a read-only retrieval operation.

Documented attack patterns abuse exactly the kind of access list_migration_version_combinations gives an agent:

How to control list_migration_version_combinations

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 list_migration_version_combinations:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_migration_version_combinations": {}
  }
}

list_migration_version_combinations is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register SousChef — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_migration_version_combinations

What does the list_migration_version_combinations tool do? +

list_migration_version_combinations. It is categorised as a Read tool in the SousChef MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_migration_version_combinations? +

Register the SousChef MCP server in PolicyLayer and add a rule for list_migration_version_combinations: 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.

What risk level is list_migration_version_combinations? +

list_migration_version_combinations is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_migration_version_combinations? +

Yes. Add a rate_limit block to the list_migration_version_combinations 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.

How do I block list_migration_version_combinations completely? +

Set action: deny in the PolicyLayer policy for list_migration_version_combinations. 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.

What MCP server provides list_migration_version_combinations? +

list_migration_version_combinations 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.

Enforce policy on every SousChef tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.