interrupt_batch · Ai Mcp Terminal MCP: Risk & Policy

WHAT IT DOES

What interrupt_batch does on Ai Mcp Terminal

AI agents invoke interrupt_batch to trigger actions in Ai Mcp Terminal. 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 interrupt_batch needs a policy

The description is empty, so classification relies on the tool name and server context. 'interrupt_batch' likely sends interrupt signals (e.g., SIGINT/Ctrl+C) to running batch processes across potentially many concurrent terminals. On a server supporting up to 100 concurrent terminals with batch operations, interrupting batches could affect multiple running processes simultaneously.

From the tool's definition Tool name 'interrupt_batch' on a terminal management server with sibling tools like 'execute_batch', 'broadcast_command', and 'execute_command'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

interrupt_batch Rate-limited

interrupt_batch 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": {
    "interrupt_batch": {
      "limits": [
        {
          "counter": "interrupt_batch_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 Ai Mcp Terminal, so you can run agents against it safely.

FAQ

Questions about interrupt_batch

What does the interrupt_batch tool do? +

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

How do I enforce a policy on interrupt_batch? +

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

What risk level is interrupt_batch? +

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

Can I rate-limit interrupt_batch? +

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

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

interrupt_batch is provided by the Ai Mcp Terminal MCP server (kanniganfan/ai-mcp-terminal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.