List all available windows across all workspaces.
AI agents call cond_list_windows to retrieve information from TermPipe MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and lists data about available windows without causing side effects, creating, modifying, deleting, or executing operations. This is a passive information-gathering operation, making it a Read category tool. Severity is low because listing windows poses minimal risk—an AI agent cannot meaningfully misuse this to cause harm, though the information could theoretically inform further actions.
From the tool's definition Tool name 'cond_list_windows' and description 'List all available windows across all workspaces' indicate a read-only query operation that retrieves window information without modification or execution.
Attacks that exploit this kind of access
List all available windows across all workspaces. It is categorised as a Read tool in the TermPipe MCP MCP Server, which means it retrieves data without modifying state.
Register the TermPipe MCP server in PolicyLayer and add a rule for cond_list_windows: 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.
cond_list_windows is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cond_list_windows 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.
Set action: deny in the PolicyLayer policy for cond_list_windows. 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.
cond_list_windows 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →