send_input · Interactive Automation MCP Server MCP

WHAT IT DOES

What send_input does on Interactive Automation MCP Server

AI agents invoke send_input to trigger actions in Interactive Automation 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.

THE RISK

High Risk

Why send_input needs a policy

The tool name 'send_input' combined with the server context (terminal automation, SSH sessions, interactive program control) strongly suggests this sends keystrokes/commands to running terminal sessions or interactive programs. This constitutes execution of arbitrary commands in live environments.

From the tool's definition Tool name 'send_input' on a server designed for 'expect/pexpect-style automation for interactive programs, supporting complex interactions with terminal programs, SSH sessions, databases, and debugging workflows'

Documented attack patterns abuse exactly the kind of access send_input gives an agent:

POLICY

How to control send_input

PolicyLayer is an MCP gateway — it sits between your AI agents and Interactive Automation MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for send_input:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_input": {
      "limits": [
        {
          "counter": "send_input_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

send_input 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.

Create a free account and register Interactive Automation MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Interactive Automation MCP Server tools

Destructive exit_terminal exit_terminal Execute open_terminal open_terminal Read await_output await_output Read get_screen_content get_screen_content Read list_terminal_sessions list_terminal_sessions

All 6 Interactive Automation MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Interactive Automation MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about send_input

What does the send_input tool do? +

send_input. It is categorised as a Execute tool in the Interactive Automation 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 send_input? +

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

What risk level is send_input? +

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

Can I rate-limit send_input? +

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

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

send_input is provided by the Interactive Automation MCP Server MCP server (wehnsdaefflae/terminal-control-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Interactive Automation MCP Server tool call.

Start from Interactive Automation MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

6 Interactive Automation MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.