query_salt_master
AI agents invoke query_salt_master to trigger actions in SousChef. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool name suggests interaction with a Salt Master, which is a central control node for infrastructure automation. 'Query' could imply read-only operations, but interacting with a Salt Master can trigger remote execution across many nodes. The description is empty, which significantly lowers confidence.
From the tool's definition Tool name: 'query_salt_master' — no description provided
Documented attack patterns abuse exactly the kind of access query_salt_master 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 query_salt_master:
{
"version": "1",
"default": "deny",
"tools": {
"query_salt_master": {
"limits": [
{
"counter": "query_salt_master_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}query_salt_master stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
query_salt_master. It is categorised as a Execute tool in the SousChef MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SousChef MCP server in PolicyLayer and add a rule for query_salt_master: 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.
query_salt_master is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the query_salt_master 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 query_salt_master. 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.
query_salt_master 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.