wbind_launch_and_focus · TermPipe MCP: Risk & Policy

WHAT IT DOES

What wbind_launch_and_focus does on TermPipe MCP

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

Launching applications is an Execute action—it runs code/processes external to the system and can have arbitrary side effects depending on the application argument. The severity is high because a malicious actor could launch harmful applications, access sensitive programs, or trigger unintended system-wide behaviors.

From the tool's definition Tool description states 'Launch an app and bring it to a known state.' The verb 'Launch' indicates execution of external applications.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wbind_launch_and_focus Rate-limited

wbind_launch_and_focus 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": {
    "wbind_launch_and_focus": {
      "limits": [
        {
          "counter": "wbind_launch_and_focus_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 wbind_launch_and_focus

What does the wbind_launch_and_focus tool do? +

Launch an app and bring it to a known state. 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 wbind_launch_and_focus? +

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

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

Can I rate-limit wbind_launch_and_focus? +

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

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

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