send_signal_to_session · Repl MCP: Risk & Policy

WHAT IT DOES

What send_signal_to_session does on Repl

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

WHY IT NEEDS A POLICY

Why send_signal_to_session needs a policy

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_signal_to_session Rate-limited

send_signal_to_session 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": {
    "send_signal_to_session": {
      "limits": [
        {
          "counter": "send_signal_to_session_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 Repl, so you can run agents against it safely.

FAQ

Questions about send_signal_to_session

What does the send_signal_to_session tool do? +

Send a signal (like Ctrl+C, Ctrl+Z) to a REPL session process. Can be used even when session is executing to interrupt long-running commands. It is categorised as a Write tool in the Repl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on send_signal_to_session? +

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

What risk level is send_signal_to_session? +

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

Can I rate-limit send_signal_to_session? +

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

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

send_signal_to_session is provided by the Repl MCP server (takafu/repl-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.