terminal_stop · Electron Terminal MCP Server MCP

WHAT IT DOES

What terminal_stop does on Electron Terminal MCP Server

AI agents invoke terminal_stop to trigger actions in Electron Terminal MCP Server. 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 terminal_stop needs a policy

Although the description is empty, the context shows this is a terminal management tool on a system that executes arbitrary commands. Stopping a terminal session is an Execute action (triggers an external operation whose effects depend on arguments—which session to stop). It is not Destructive because it does not irreversibly delete data, but it does interrupt running operations.

From the tool's definition The tool 'terminal_stop' is part of a terminal server that 'enables clients to interact with a system terminal' and allows 'executing commands, managing terminal sessions'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

terminal_stop Rate-limited

terminal_stop 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": {
    "terminal_stop": {
      "limits": [
        {
          "counter": "terminal_stop_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 Electron Terminal MCP Server, so you can run agents against it safely.

FAQ

Questions about terminal_stop

What does the terminal_stop tool do? +

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

How do I enforce a policy on terminal_stop? +

Register the Electron Terminal MCP Server MCP server in PolicyLayer and add a rule for terminal_stop: 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 Electron Terminal MCP Server. Nothing to install.

What risk level is terminal_stop? +

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

Can I rate-limit terminal_stop? +

Yes. Add a rate_limit block to the terminal_stop 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 terminal_stop completely? +

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

terminal_stop is provided by the Electron Terminal MCP Server MCP server (nexon33/console-terminal-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.