Low Risk

list_puppet_server_nodes

List Puppet nodes available from a certificate-authenticated connector.

How to control list_puppet_server_nodes ↓

What list_puppet_server_nodes does on SousChef

AI agents call list_puppet_server_nodes 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 list_puppet_server_nodes needs a policy

This tool queries and retrieves information about Puppet nodes from a server using certificate authentication. It performs a read-only operation that enumerates existing infrastructure state without creating, modifying, executing, or deleting anything. The blast radius of misuse is minimal—an agent could discover node names and metadata, but cannot alter infrastructure or cause damage.

From the tool's definition Tool name 'list_puppet_server_nodes' and description 'List Puppet nodes' indicate a retrieval/enumeration operation with no modification or execution capability.

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

How to control list_puppet_server_nodes

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

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

list_puppet_server_nodes 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 list_puppet_server_nodes

What does the list_puppet_server_nodes tool do? +

List Puppet nodes available from a certificate-authenticated connector. 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 list_puppet_server_nodes? +

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

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

Can I rate-limit list_puppet_server_nodes? +

Yes. Add a rate_limit block to the list_puppet_server_nodes 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 list_puppet_server_nodes completely? +

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

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