cond_launch · TermPipe MCP: Risk & Policy

WHAT IT DOES

What cond_launch does on TermPipe MCP

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

Launching arbitrary applications is an Execute action: it runs external code/processes whose effects depend on which application is launched and how it behaves. While not immediately destructive, the blast radius is high because a compromised AI could launch malicious or resource-intensive applications, alter system state, exfiltrate data, or chain attacks.

From the tool's definition Tool description states 'Launch an application by name' — this directly triggers execution of external applications.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cond_launch Rate-limited

cond_launch 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": {
    "cond_launch": {
      "limits": [
        {
          "counter": "cond_launch_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 cond_launch

What does the cond_launch tool do? +

Launch an application by name (uses cond app database, fuzzy match). 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 cond_launch? +

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

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

Can I rate-limit cond_launch? +

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

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

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