boot · TermPipe MCP: Risk & Policy

WHAT IT DOES

What boot does on TermPipe MCP

AI agents invoke boot 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 boot needs a policy

The tool description is vague ('mid-session context refresh with integrated briefing'), but given the server context — which explicitly provides terminal access, command execution, and automated installation scripts — a 'boot' operation on such a server likely triggers some form of initialization or re-execution sequence.

From the tool's definition 'Mid-session context refresh with integrated briefing' on a server that provides 'direct terminal access to execute commands' and 'automated installation scripts'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

boot Rate-limited

boot 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": {
    "boot": {
      "limits": [
        {
          "counter": "boot_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 boot

What does the boot tool do? +

Mid-session context refresh with integrated briefing. 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 boot? +

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

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

Can I rate-limit boot? +

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

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

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