create_terminal_basic · Persistent Terminal MCP Server MCP

WHAT IT DOES

What create_terminal_basic does on Persistent Terminal MCP Server

AI agents invoke create_terminal_basic 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 create_terminal_basic needs a policy

Creating a persistent terminal session spawns a shell process that can execute arbitrary commands. While the act of creation itself is a setup step, the resulting session enables arbitrary code/command execution. The persistence aspect increases blast radius as sessions continue running after disconnection.

From the tool's definition Create a new persistent terminal session (shell and cwd only)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_terminal_basic Rate-limited

create_terminal_basic 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": {
    "create_terminal_basic": {
      "limits": [
        {
          "counter": "create_terminal_basic_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 create_terminal_basic

What does the create_terminal_basic tool do? +

Create a new persistent terminal session (shell and cwd only). Useful for clients that cannot send env objects. 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 create_terminal_basic? +

Register the Persistent Terminal MCP Server MCP server in PolicyLayer and add a rule for create_terminal_basic: 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 create_terminal_basic? +

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

Can I rate-limit create_terminal_basic? +

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

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

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