AI agents invoke hide_keyboard to trigger actions in uiautomator2 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.
Based on the server context (uiautomator2 Android automation) and the tool name, this tool likely triggers a UI action to dismiss/hide the on-screen keyboard on an Android device. This is an Execute-category action as it triggers an external UI operation on the device. The description is empty, which lowers confidence. Severity is medium since misuse could disrupt UI automation flows but has limited broader impact.
From the tool's definition Tool name 'hide_keyboard' on a server that controls Android devices via uiautomator2; description is empty
Documented attack patterns abuse exactly the kind of access hide_keyboard gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and uiautomator2 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for hide_keyboard:
{
"version": "1",
"default": "deny",
"tools": {
"hide_keyboard": {
"limits": [
{
"counter": "hide_keyboard_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}hide_keyboard 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.
hide_keyboard. It is categorised as a Execute tool in the uiautomator2 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the uiautomator2 MCP Server MCP server in PolicyLayer and add a rule for hide_keyboard: 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 uiautomator2 MCP Server. Nothing to install.
hide_keyboard 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 hide_keyboard 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 hide_keyboard. 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.
hide_keyboard is provided by the uiautomator2 MCP Server MCP server (tanbro/uiautomator2-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from uiautomator2 MCP Server, 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.
77 uiautomator2 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.