Triggers a redraw of the running program by sending SIGWINCH (resize signal) to the PTY.
AI agents invoke terminal-refresh to trigger actions in Mcp Terminal. 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 sends a Unix signal (SIGWINCH) to a running process via the PTY. Sending signals to processes is an external operation that can affect process behavior. While SIGWINCH is typically benign (it notifies processes of terminal resize), signal delivery is an Execute-category action — it triggers an external operation on a running process.
From the tool's definition Triggers a redraw of the running program by sending SIGWINCH (resize signal) to the PTY
Attacks that exploit this kind of access
Triggers a redraw of the running program by sending SIGWINCH (resize signal) to the PTY. It is categorised as a Execute tool in the Mcp Terminal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Terminal MCP server in PolicyLayer and add a rule for terminal-refresh: 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 Mcp Terminal. Nothing to install.
terminal-refresh 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 terminal-refresh 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 terminal-refresh. 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.
terminal-refresh is provided by the Mcp Terminal MCP server (unfathomable-siren38/mcp-terminal-server). 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 →