Resize the terminal of an active shell session.
AI agents invoke resize_shell to trigger actions in Interactive Shell 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.
This tool modifies the terminal dimensions (rows/columns) of an active PTY session. While not directly executing commands or destroying data, it triggers an external operation (SIGWINCH signal) on a running process and changes the state of an active shell session. It's more than a read, and closest to Execute as it affects a running process's environment.
From the tool's definition Resize the terminal of an active shell session
Attacks that exploit this kind of access
Resize the terminal of an active shell session. It is categorised as a Execute tool in the Interactive Shell MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Interactive Shell MCP server in PolicyLayer and add a rule for resize_shell: 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 Interactive Shell MCP. Nothing to install.
resize_shell 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 resize_shell 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 resize_shell. 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.
resize_shell is provided by the Interactive Shell MCP server (lightos/interactive-shell-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 →