Send keystrokes to the TUI app. Use this for special keys and shortcuts, not for typing text (use send_text for that). Accepts a single key descriptor string or an array of key descriptors to send in sequence. Supports named keys (Enter, Tab, Escape, Up, Down, Left, Right, Backspace, Delete, Home...
AI agents invoke send_keys 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.
Sending keystrokes to a running TUI application can trigger arbitrary actions within that application — including executing commands, confirming destructive dialogs, navigating menus, or invoking shortcuts like Ctrl+C/Ctrl+Z.
From the tool's definition Send keystrokes to the TUI app... Supports named keys (Enter, Tab, Escape, Up, Down, Left, Right, Backspace, Delete, Home, End, PageUp, PageDown, F1-F12, Space) and modifiers (Ctrl+, Alt+, Shift+)
Documented attack patterns abuse exactly the kind of access send_keys 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_keys:
{
"version": "1",
"default": "deny",
"tools": {
"send_keys": {
"limits": [
{
"counter": "send_keys_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}send_keys 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.
Send keystrokes to the TUI app. Use this for special keys and shortcuts, not for typing text (use send_text for that). Accepts a single key descriptor string or an array of key descriptors to send in sequence. Supports named keys (Enter, Tab, Escape, Up, Down, Left, Right, Backspace, Delete, Home, End, PageUp, PageDown, F1-F12, Space) and modifiers (Ctrl+, Alt+, Shift+). Examples:. 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_keys: 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_keys 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_keys 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_keys. 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_keys 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.