send_escape_sequence · Iterm2 MCP: Risk & Policy

WHAT IT DOES

What send_escape_sequence does on Iterm2

AI agents invoke send_escape_sequence to trigger actions in Iterm2. 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.

WHY IT NEEDS A POLICY

Why send_escape_sequence needs a policy

Escape sequences sent to a terminal emulator can trigger a wide range of actions: moving the cursor, changing terminal state, manipulating the screen buffer, or in some cases interacting with the terminal in ways that could execute commands or alter session behavior.

From the tool's definition Tool name 'send_escape_sequence' on a server that provides 'full control over iTerm2 terminal sessions' and can 'run commands, read screen content, and interact with terminal sessions'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_escape_sequence Rate-limited

send_escape_sequence stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_escape_sequence": {
      "limits": [
        {
          "counter": "send_escape_sequence_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Iterm2, so you can run agents against it safely.

FAQ

Questions about send_escape_sequence

What does the send_escape_sequence tool do? +

send_escape_sequence. It is categorised as a Execute tool in the Iterm2 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on send_escape_sequence? +

Register the Iterm2 MCP server in PolicyLayer and add a rule for send_escape_sequence: 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.

What risk level is send_escape_sequence? +

send_escape_sequence is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit send_escape_sequence? +

Yes. Add a rate_limit block to the send_escape_sequence 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.

How do I block send_escape_sequence completely? +

Set action: deny in the PolicyLayer policy for send_escape_sequence. 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.

What MCP server provides send_escape_sequence? +

send_escape_sequence 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.