terminal_close · MCP Shell Server MCP: Risk & Policy

WHAT IT DOES

What terminal_close does on MCP Shell Server

AI agents use terminal_close to create or update resources in MCP Shell Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Shell Server environment.

WHY IT NEEDS A POLICY

Why terminal_close needs a policy

An AI agent can call terminal_close faster than any human can review — one bad instruction and it creates or modifies resources in MCP Shell Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

terminal_close Rate-limited

terminal_close stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_close": {
      "limits": [
        {
          "counter": "terminal_close_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Shell Server, so you can run agents against it safely.

FAQ

Questions about terminal_close

What does the terminal_close tool do? +

Close terminal session. It is categorised as a Write tool in the MCP Shell Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on terminal_close? +

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

What risk level is terminal_close? +

terminal_close is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit terminal_close? +

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

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

terminal_close is provided by the MCP Shell Server MCP server (mako10k/mcp-shell-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.