cond_visual_query · TermPipe MCP: Risk & Policy

WHAT IT DOES

What cond_visual_query does on TermPipe MCP

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

The description is empty, so classification relies on context. The server provides direct terminal access and command execution capabilities. The 'cond_' prefix suggests it's part of a conditional/terminal management family (alongside cond_close, cond_clipboard_get, etc.), and 'visual_query' likely involves querying or interacting with a terminal display or visual buffer.

From the tool's definition Tool name 'cond_visual_query' on a server that 'provides AI assistants with direct terminal access to execute commands, manage files, and run persistent REPL sessions'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cond_visual_query Rate-limited

cond_visual_query 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_visual_query": {
      "limits": [
        {
          "counter": "cond_visual_query_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_visual_query

What does the cond_visual_query tool do? +

cond_visual_query. 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_visual_query? +

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

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

Can I rate-limit cond_visual_query? +

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

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

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