Type a string of characters into the TUI app. The text is sent exactly as provided - MCP JSON handles escaping, so do not double-escape. To type a literal backslash, send one backslash. Include a trailing newline (\\n) if you want to press Enter after the text. Use send_keys instead for special k...
AI agents invoke send_text to trigger actions in Tui. 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.
This tool sends arbitrary text input to a running TUI application, effectively controlling it as if a user were typing. Depending on the application receiving the input, this could execute commands, confirm destructive operations, submit forms, or trigger any other application behavior. The ability to send Enter keypresses means commands can be fully executed.
From the tool's definition 'Type a string of characters into the TUI app' and 'Include a trailing newline (\n) if you want to press Enter after the text'
Documented attack patterns abuse exactly the kind of access send_text gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tui, and nothing reaches the server without passing your rules. This is the rule we recommend for send_text:
{
"version": "1",
"default": "deny",
"tools": {
"send_text": {
"limits": [
{
"counter": "send_text_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}send_text 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.
Free to start. No card required.
Type a string of characters into the TUI app. The text is sent exactly as provided - MCP JSON handles escaping, so do not double-escape. To type a literal backslash, send one backslash. Include a trailing newline (\\n) if you want to press Enter after the text. Use send_keys instead for special keys like Ctrl+C or arrow keys. It is categorised as a Execute tool in the Tui MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Tui 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 Tui. 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 Tui MCP server (nvms/tui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tui, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Tui tools catalogued and risk-classified — across an index of 43,000+ MCP servers.