bash_pipe

What bash_pipe does on MCP Filesystem Server

AI agents invoke bash_pipe to trigger actions in MCP Filesystem 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 bash_pipe is rated High

This tool executes shell commands with potential side effects determined by the piped command arguments. It is not a simple read operation (it executes, not queries), not primarily for data modification via standard CRUD (it runs arbitrary system commands), and not explicitly destructive unless the piped commands themselves perform destructive operations—making Execute the appropriate category.

From the tool's definition Tool name 'bash_pipe' and description 'Execute a sequence of Bash commands piped together' explicitly indicates execution of arbitrary bash command sequences. The piping mechanism allows chaining commands with full shell capabilities.

The rule that runs bash_pipe safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Filesystem Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bash_pipe, this is the rule to start with:

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

Questions about bash_pipe