open_terminal_ui · Persistent Terminal MCP Server MCP

WHAT IT DOES

What open_terminal_ui does on Persistent Terminal MCP Server

AI agents invoke open_terminal_ui to trigger actions in Persistent 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 open_terminal_ui needs a policy

This tool launches a browser or opens a URL to display a web-based UI, which constitutes an external operation/browser action. While it is primarily a view/read interface for terminal sessions, the act of opening a browser window is an Execute-level side effect.

From the tool's definition 'Open a web-based terminal management UI in the browser' — triggers an external browser action to open a web UI

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

open_terminal_ui Rate-limited

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

FAQ

Questions about open_terminal_ui

What does the open_terminal_ui tool do? +

Open a web-based terminal management UI in the browser. This provides a visual interface to manage all terminal sessions. It is categorised as a Execute tool in the Persistent 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 open_terminal_ui? +

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

What risk level is open_terminal_ui? +

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

Can I rate-limit open_terminal_ui? +

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

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

open_terminal_ui is provided by the Persistent Terminal MCP Server MCP server (masx200/persistent-terminal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.