Send a mouse event to the TUI app (if the app has mouse support enabled).
AI agents invoke send_mouse 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 triggers external operations by sending mouse events to a running TUI application. The effects depend on what the target application does in response to mouse clicks/movements, making it an Execute-category action. Misuse could trigger arbitrary application-level actions depending on what's running in the terminal session.
From the tool's definition Send a mouse event to the TUI app (if the app has mouse support enabled)
Documented attack patterns abuse exactly the kind of access send_mouse 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_mouse:
{
"version": "1",
"default": "deny",
"tools": {
"send_mouse": {
"limits": [
{
"counter": "send_mouse_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} send_mouse 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 a mouse event to the TUI app (if the app has mouse support enabled). 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_mouse: 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_mouse 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_mouse 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_mouse. 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_mouse 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.