AI agents call get_chef_roles 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.
This tool retrieves or queries Chef role data as part of infrastructure analysis. The 'get_' prefix strongly suggests read-only retrieval of existing Chef configuration data. With no description stating otherwise and given the migration assessment context, this is a Read category tool.
From the tool's definition Tool name is 'get_chef_roles' which follows the 'get_' prefix pattern indicating data retrieval. No description provided, but the verb 'get' and context within a Chef-to-Ansible migration tool suite (analysing and assessing existing Chef infrastructure)…
Documented attack patterns abuse exactly the kind of access get_chef_roles 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_chef_roles:
{
"version": "1",
"default": "deny",
"tools": {
"get_chef_roles": {}
}
}get_chef_roles 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_chef_roles. 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_chef_roles: 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_chef_roles 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_chef_roles 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_chef_roles. 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_chef_roles 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.