// SCAN REPORT

Interactive Terminal MCP

4 tools. 3 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 12 Jun 2026

3 can modify or destroy data

1 read-only

4 tools total

Community server · catalogue entry verified 12/06/2026

How to control Interactive Terminal MCP ↓

TOOL MAP

What Interactive Terminal MCP exposes to your agents

Read (1) Write / Execute (2) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Interactive Terminal MCP tools

Destructive · High kill_session Killing a process and cleaning up its resources is an irreversible action. Execute · Critical send_command The server's purpose is to run arbitrary terminal commands in persistent sessions. Execute · Critical spawn_process Spawning an interactive CLI process is an Execute-category action with critical severity.

3 of Interactive Terminal MCP's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Interactive Terminal MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and Interactive Terminal MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "kill_session": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Cap read operations

{
  "read_buffer": {
    "limits": [
      {
        "counter": "read_buffer_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Interactive Terminal MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON INTERACTIVE TERMINAL →

Free to start. No card required.

FULL CATALOGUE

All 4 Interactive Terminal MCP tools

DESTRUCTIVE 1 tools

Destructive kill_session Terminates the process and cleans up resources.

EXECUTE 2 tools

Execute send_command send_command Execute spawn_process Spawns a new interactive CLI process.

READ 1 tools

Read read_buffer Reads remaining content from the buffer without sending a command.

FAQ

Questions about Interactive Terminal MCP

Can an AI agent delete data through the Interactive Terminal MCP server? +

Yes. The Interactive Terminal MCP server exposes 1 destructive tools including kill_session. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How many tools does the Interactive Terminal MCP server expose? +

4 tools across 2 categories: Read, Write. 1 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Interactive Terminal MCP? +

Register the Interactive Terminal MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Interactive Terminal MCP tool call.

Deterministic rules across all 4 Interactive Terminal MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON INTERACTIVE TERMINAL →

Free to start. No card required.

4 Interactive Terminal MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.