get_version_combination_info
AI agents call get_version_combination_info 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.
The tool name structure ('get_' + informational query) implies reading version combination metadata without side effects. In the context of a Chef-to-Ansible migration tool, this likely retrieves compatibility or version information. No evidence of writes, execution, deletion, or financial operations. Default to Read category with reduced confidence due to empty description.
From the tool's definition Tool name 'get_version_combination_info' indicates a retrieval operation. The 'get_' prefix and lack of mutation/execution keywords suggest data querying. Description is empty, which reduces confidence slightly.
Documented attack patterns abuse exactly the kind of access get_version_combination_info 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 get_version_combination_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_version_combination_info": {}
}
}get_version_combination_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_version_combination_info. It is categorised as a Read tool in the SousChef MCP Server, which means it retrieves data without modifying state.
Register the SousChef MCP server in PolicyLayer and add a rule for get_version_combination_info: 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.
get_version_combination_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_version_combination_info 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 get_version_combination_info. 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.
get_version_combination_info 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.