Low Risk

analyse_cookbook_dependencies

analyse_cookbook_dependencies

How to control analyse_cookbook_dependencies ↓

What analyse_cookbook_dependencies does on SousChef

AI agents call analyse_cookbook_dependencies 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.

Low Risk

Why analyse_cookbook_dependencies needs a policy

This tool performs dependency analysis, a typical Read operation that retrieves and examines data structures. No side effects (creation, modification, deletion, or execution) are indicated by the name. The empty description lowers confidence slightly, but the name strongly suggests introspection of cookbook metadata.

From the tool's definition Tool name 'analyse_cookbook_dependencies' indicates static analysis of Chef cookbook dependency structures.

Documented attack patterns abuse exactly the kind of access analyse_cookbook_dependencies gives an agent:

How to control analyse_cookbook_dependencies

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 analyse_cookbook_dependencies:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "analyse_cookbook_dependencies": {}
  }
}

analyse_cookbook_dependencies is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register SousChef — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about analyse_cookbook_dependencies

What does the analyse_cookbook_dependencies tool do? +

analyse_cookbook_dependencies. It is categorised as a Read tool in the SousChef MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on analyse_cookbook_dependencies? +

Register the SousChef MCP server in PolicyLayer and add a rule for analyse_cookbook_dependencies: 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.

What risk level is analyse_cookbook_dependencies? +

analyse_cookbook_dependencies is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit analyse_cookbook_dependencies? +

Yes. Add a rate_limit block to the analyse_cookbook_dependencies 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.

How do I block analyse_cookbook_dependencies completely? +

Set action: deny in the PolicyLayer policy for analyse_cookbook_dependencies. 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.

What MCP server provides analyse_cookbook_dependencies? +

analyse_cookbook_dependencies 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.

Enforce policy on every SousChef tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.