Resizes the PTY to match the UI terminal dimensions.
AI agents invoke terminal-resize 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.
Resizing a PTY (pseudo-terminal) is an operational action that modifies the terminal session's state. While it doesn't run code or delete data, it does trigger an external operation affecting a live terminal session. The blast radius is low since resizing a terminal is reversible and has minimal side effects, but it does interact with an active process/session beyond simple data retrieval or storage.
From the tool's definition Resizes the PTY to match the UI terminal dimensions
Attacks that exploit this kind of access
Resizes the PTY to match the UI terminal dimensions. 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-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 Mcp Terminal. 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 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 →