cond_type · TermPipe MCP: Risk & Policy

WHAT IT DOES

What cond_type does on TermPipe MCP

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

Injecting keystrokes into the active window via compositor-level input is an Execute-category action. The tool can drive arbitrary UI interactions — including typing commands into terminals, browsers, editors — making it high severity since a malicious or mistaken payload could trigger destructive or financial operations in the target application.

From the tool's definition 'Type text into the active window via compositor input injection' — this triggers external operations by injecting input into whatever window is currently active, with effects entirely dependent on arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cond_type Rate-limited

cond_type 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_type": {
      "limits": [
        {
          "counter": "cond_type_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_type

What does the cond_type tool do? +

Type text into the active window via compositor input injection. 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_type? +

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

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

Can I rate-limit cond_type? +

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

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

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