AI agents invoke wait_for_output to trigger actions in PiloTY. 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.
This tool enables monitoring and interaction with shell command execution. While the description is empty, the server context makes clear this facilitates Execute operations—it waits for output from commands sent via sibling tools like `send_line` and `send_text`. Misuse could allow an AI agent to wait indefinitely, trigger race conditions, or coordinate with other terminal tools to execute arbitrary code.
From the tool's definition Tool `wait_for_output` is part of PiloTY, an MCP server providing 'persistent, interactive terminal' capabilities with 'long-running commands' and 'shell interactions'.
Documented attack patterns abuse exactly the kind of access wait_for_output gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PiloTY, and nothing reaches the server without passing your rules. This is the rule we recommend for wait_for_output:
{
"version": "1",
"default": "deny",
"tools": {
"wait_for_output": {
"limits": [
{
"counter": "wait_for_output_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}wait_for_output 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.
Free to start. No card required.
wait_for_output. It is categorised as a Execute tool in the PiloTY MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PiloTY MCP server in PolicyLayer and add a rule for wait_for_output: 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 PiloTY. Nothing to install.
wait_for_output is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wait_for_output 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 wait_for_output. 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.
wait_for_output is provided by the PiloTY MCP server (yiwenlu66/piloty). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 PiloTY tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
17 PiloTY tools catalogued and risk-classified — across an index of 42,500+ MCP servers.