parse_salt_directory
AI agents call parse_salt_directory 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 name suggests reading/parsing a Salt configuration directory, which would be a read operation. However, the description is empty, limiting confidence. In context of a Chef-to-Ansible migration server, this likely reads and analyzes Salt configuration files. Severity is medium because parsing infrastructure configuration could expose sensitive infrastructure details.
From the tool's definition Tool name 'parse_salt_directory' — no description provided.
Documented attack patterns abuse exactly the kind of access parse_salt_directory 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 parse_salt_directory:
{
"version": "1",
"default": "deny",
"tools": {
"parse_salt_directory": {}
}
}parse_salt_directory 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.
parse_salt_directory. 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 parse_salt_directory: 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.
parse_salt_directory 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 parse_salt_directory 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 parse_salt_directory. 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.
parse_salt_directory 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.