build · TermPipe MCP: Risk & Policy

WHAT IT DOES

What build does on TermPipe MCP

AI agents invoke build to trigger actions in TermPipe MCP. 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 build needs a policy

Build tools execute code with arbitrary effects depending on arguments (compilation, test execution, deployment triggers). Given the TermPipe server's core purpose of terminal command execution and the tool's position among file manipulation and process control functions, this is an Execute risk.

From the tool's definition Server description states 'Provides AI assistants with direct terminal access to execute commands' and lists sibling tools including file operations and daemon management.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

build Rate-limited

build 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": {
    "build": {
      "limits": [
        {
          "counter": "build_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 TermPipe MCP, so you can run agents against it safely.

FAQ

Questions about build

What does the build tool do? +

build. It is categorised as a Execute tool in the TermPipe MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on build? +

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

What risk level is build? +

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

Can I rate-limit build? +

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

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

build is provided by the TermPipe MCP server (wbind-core/termpipe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.