confirm_command · Linux MCP Server MCP: Risk & Policy

WHAT IT DOES

What confirm_command does on Linux MCP Server

AI agents invoke confirm_command to trigger actions in Linux 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 confirm_command needs a policy

This tool proceeds with executing a command that was previously flagged as dangerous. While it adds a confirmation step, its ultimate action is executing a dangerous Linux command via SSH. The 'previously flagged dangerous' qualifier means the underlying operation is high-risk (could be destructive, system-altering, etc.).

From the tool's definition 'confirm the execution of a previously flagged dangerous command' — this tool triggers execution of commands that were already identified as dangerous

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

confirm_command Rate-limited

confirm_command 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": {
    "confirm_command": {
      "limits": [
        {
          "counter": "confirm_command_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 Linux MCP Server, so you can run agents against it safely.

FAQ

Questions about confirm_command

What does the confirm_command tool do? +

Prompt the user to confirm the execution of a previously flagged dangerous command. It is categorised as a Execute tool in the Linux 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 confirm_command? +

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

What risk level is confirm_command? +

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

Can I rate-limit confirm_command? +

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

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

confirm_command is provided by the Linux MCP Server MCP server (jnprautomate/linux-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.