# sessions

A execute tool on the iTerm MCP MCP server.

Agent View of the PolicyLayer registry record for `sessions`. HTML page: https://policylayer.com/tools/research-developer-iterm-mcp-claude-agency/sessions

## Facts

- Tool: `sessions`
- Server: iTerm MCP (`research-developer/iterm-mcp-claude-agency`) — https://policylayer.com/tools/research-developer-iterm-mcp-claude-agency.md
- Homepage: https://github.com/research-developer/iterm-mcp-claude-agency
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "sessions",
    "arguments": {}
  }
}
```

## Why sessions is rated High

Session management for a terminal application like iTerm2 falls under Execute because it allows orchestration and control of terminal environments where arbitrary commands can be run.

From the tool's own definition: "Tool 'sessions' on iTerm MCP server that 'Controls iTerm2 terminal sessions with multi-pane support, allowing parallel command execution, session management' — managing terminal sessions inherently enables command execution and control of shell environments."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches iTerm MCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "sessions": {
      "limits": [
        {
          "counter": "sessions_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on iTerm MCP (15)

- `delegate` — Execute — https://policylayer.com/tools/research-developer-iterm-mcp-claude-agency/delegate.md
- `managers` — Execute — https://policylayer.com/tools/research-developer-iterm-mcp-claude-agency/managers.md
- `orchestrate` — Execute — https://policylayer.com/tools/research-developer-iterm-mcp-claude-agency/orchestrate.md
- `roles` — Execute — https://policylayer.com/tools/research-developer-iterm-mcp-claude-agency/roles.md
- `services` — Execute — https://policylayer.com/tools/research-developer-iterm-mcp-claude-agency/services.md
- `telemetry` — Execute — https://policylayer.com/tools/research-developer-iterm-mcp-claude-agency/telemetry.md
- `wait_for` — Execute — https://policylayer.com/tools/research-developer-iterm-mcp-claude-agency/wait-for.md
- `workflows` — Execute — https://policylayer.com/tools/research-developer-iterm-mcp-claude-agency/workflows.md
- `agents` — Other — https://policylayer.com/tools/research-developer-iterm-mcp-claude-agency/agents.md
- `bus` — Other — https://policylayer.com/tools/research-developer-iterm-mcp-claude-agency/bus.md
- `feedback` — Other — https://policylayer.com/tools/research-developer-iterm-mcp-claude-agency/feedback.md
- `memory` — Other — https://policylayer.com/tools/research-developer-iterm-mcp-claude-agency/memory.md
- `messages` — Other — https://policylayer.com/tools/research-developer-iterm-mcp-claude-agency/messages.md
- `subscribe` — Other — https://policylayer.com/tools/research-developer-iterm-mcp-claude-agency/subscribe.md
- `teams` — Other — https://policylayer.com/tools/research-developer-iterm-mcp-claude-agency/teams.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=research-developer-iterm-mcp-claude-agency · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/research-developer-iterm-mcp-claude-agency