ssh_puppet_noop · SSH MCP Server MCP: Risk & Policy

WHAT IT DOES

What ssh_puppet_noop does on SSH MCP Server

AI agents invoke ssh_puppet_noop to trigger actions in SSH MCP Server. 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.

WHY IT NEEDS A POLICY

Why ssh_puppet_noop needs a policy

Although 'no-op' mode is non-destructive (dry-run, no actual changes applied), this tool still Execute-level because it: (1) triggers Puppet agent operations on remote systems, (2) the effects and scope depend on Puppet manifests/configuration (arguments to Puppet), and (3) misuse could enumerate or probe system state in ways that inform subsequent attacks.

From the tool's definition Tool runs 'Puppet agent in no-op mode' — executes external system management operations via SSH. The server description states it 'Enables remote Linux server management via SSH, allowing command execution.' Puppet is a configuration management tool that…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ssh_puppet_noop Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ssh_puppet_noop": {
      "limits": [
        {
          "counter": "ssh_puppet_noop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches SSH MCP Server, so you can run agents against it safely.

FAQ

Questions about ssh_puppet_noop

What does the ssh_puppet_noop tool do? +

Run Puppet agent in no-op mode (dry run) with verbose output. It is categorised as a Execute tool in the SSH MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ssh_puppet_noop? +

Register the SSH MCP Server MCP server in PolicyLayer and add a rule for ssh_puppet_noop: 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 SSH MCP Server. Nothing to install.

What risk level is ssh_puppet_noop? +

ssh_puppet_noop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ssh_puppet_noop? +

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

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

ssh_puppet_noop is provided by the SSH MCP Server MCP server (inframcp/ssh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.