v1.0.2: Quick send text to terminal (convenience method of send_keys). Sends string directly, not parsed as key. Suitable for quick text input
AI agents invoke send_text 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.
Sending text to a terminal can trigger command execution depending on what is already running or waiting for input. In the context of a multi-threaded terminal management server that supports async command execution, injecting arbitrary text into a terminal is effectively an Execute-level action.
From the tool's definition 'send text to terminal' and 'Quick send text to terminal (convenience method of send_keys)' — sends arbitrary text/input directly to a terminal session
Attacks that exploit this kind of access
v1.0.2: Quick send text to terminal (convenience method of send_keys). Sends string directly, not parsed as key. Suitable for quick text input. 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.
Register the Ai Mcp Terminal MCP server in PolicyLayer and add a rule for send_text: 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.
send_text is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the send_text 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.
Set action: deny in the PolicyLayer policy for send_text. 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.
send_text 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →