Convert InSpec controls to test framework format.
AI agents use convert_inspec_to_test 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.
This tool generates or rewrites test files by transforming InSpec controls into a different test framework format. This is a reversible modification operation (Write category). Severity is medium because misuse could corrupt test definitions or create incorrect test coverage, affecting infrastructure validation integrity.
From the tool's definition Tool converts InSpec controls to test framework format—a transformation that creates or modifies test code artifacts. The verb 'convert' indicates data modification rather than read-only analysis or destructive deletion.
Documented attack patterns abuse exactly the kind of access convert_inspec_to_test 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 convert_inspec_to_test:
{
"version": "1",
"default": "deny",
"tools": {
"convert_inspec_to_test": {
"limits": [
{
"counter": "convert_inspec_to_test_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}convert_inspec_to_test 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.
Convert InSpec controls to test framework format. 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 convert_inspec_to_test: 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.
convert_inspec_to_test 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 convert_inspec_to_test 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 convert_inspec_to_test. 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.
convert_inspec_to_test 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.