AI agents use create_window to create or update resources in Iterm2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iterm2 environment.
This tool creates a new terminal window in iTerm2, which is a reversible write action. It does not execute commands, delete data, or have financial implications. The blast radius is low since creating an empty window is benign and easily closed.
From the tool's definition Create a new iTerm2 window
Attacks that exploit this kind of access
Create a new iTerm2 window. It is categorised as a Write tool in the Iterm2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Iterm2 MCP server in PolicyLayer and add a rule for create_window: 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 Iterm2. Nothing to install.
create_window is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_window 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 create_window. 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.
create_window is provided by the Iterm2 MCP server (lorencarvalho/iterm2-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
create_window is one line of Iterm2's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →