generate_handler_routing_config
AI agents use generate_handler_routing_config to create or update resources in SousChef — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SousChef environment.
The tool appears to generate (create) handler routing configuration, likely for Chef or Ansible infrastructure. This is a Write operation because it produces new configuration artifacts that can be modified or replaced. It is not Destructive (no deletion), Execute (no arbitrary code/command execution with variable effects), or Financial.
From the tool's definition Tool name 'generate_handler_routing_config' indicates it creates or produces configuration data. The 'generate_' prefix and 'config' suffix strongly suggest file/data creation.
Documented attack patterns abuse exactly the kind of access generate_handler_routing_config 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 generate_handler_routing_config:
{
"version": "1",
"default": "deny",
"tools": {
"generate_handler_routing_config": {
"limits": [
{
"counter": "generate_handler_routing_config_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}generate_handler_routing_config stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
generate_handler_routing_config. It is categorised as a Write tool in the SousChef MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SousChef MCP server in PolicyLayer and add a rule for generate_handler_routing_config: 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.
generate_handler_routing_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_handler_routing_config 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 generate_handler_routing_config. 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.
generate_handler_routing_config 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.