Resize an existing interactive terminal session.
AI agents invoke terminal-resize to trigger actions in TermSSH 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.
Resizing a terminal session is an operational action that affects an active remote session's dimensions. It doesn't read data, write files, or destroy anything, but it does interact with and alter the state of a live execution environment (an SSH terminal session). The blast radius is low since resizing alone doesn't cause data loss or financial impact, but it is part of a remote execution context.
From the tool's definition 'Resize an existing interactive terminal session' — modifies the state of a running terminal session on a remote SSH connection
Attacks that exploit this kind of access
Resize an existing interactive terminal session. It is categorised as a Execute tool in the TermSSH MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TermSSH MCP server in PolicyLayer and add a rule for terminal-resize: 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 TermSSH MCP. Nothing to install.
terminal-resize 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-resize 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-resize. 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-resize is provided by the TermSSH MCP server (rayss868/termssh-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 →