stop_repl · Replit MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_repl does on Replit MCP Server

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

This tool triggers an external operation (stopping a workspace) whose effects depend on which repl is targeted. While not destructive (the repl data persists) or financial, it is an Execute action because it performs a state-changing operational command on a running system. Severity is medium because stopping a repl interrupts work and could disrupt services, but does not cause data loss or irreversible damage.

From the tool's definition Tool name 'stop_repl' and description 'Stop a running Replit workspace' indicate an action that terminates a running process/service. Stopping a repl is an operational action that changes system state by halting execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_repl Rate-limited

stop_repl 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": {
    "stop_repl": {
      "limits": [
        {
          "counter": "stop_repl_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 Replit MCP Server, so you can run agents against it safely.

FAQ

Questions about stop_repl

What does the stop_repl tool do? +

Stop a running Replit workspace. It is categorised as a Execute tool in the Replit 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 stop_repl? +

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

What risk level is stop_repl? +

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

Can I rate-limit stop_repl? +

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

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

stop_repl is provided by the Replit MCP Server MCP server (nova-3951/replit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.