terminal_execute · Mcp Shellkeeper MCP: Risk & Policy

WHAT IT DOES

What terminal_execute does on Mcp Shellkeeper

AI agents invoke terminal_execute to trigger actions in Mcp Shellkeeper. 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_execute needs a policy

This tool permits execution of arbitrary shell commands on a remote system (via SSH support noted in server description), which constitutes code execution with externally-determined effects. The blast radius is critical because a misguided agent could execute destructive, malicious, or data-exfiltrating commands.

From the tool's definition Tool name and description: 'Execute a command in a persistent terminal session.' Explicitly executes arbitrary commands via terminal with SSH support.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

terminal_execute Rate-limited

terminal_execute 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_execute": {
      "limits": [
        {
          "counter": "terminal_execute_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 Mcp Shellkeeper, so you can run agents against it safely.

FAQ

Questions about terminal_execute

What does the terminal_execute tool do? +

Execute a command in a persistent terminal session. It is categorised as a Execute tool in the Mcp Shellkeeper 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_execute? +

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

What risk level is terminal_execute? +

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

Can I rate-limit terminal_execute? +

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

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

terminal_execute is provided by the Mcp Shellkeeper MCP server (mcp-shellkeeper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.