adb_input_text
Type text on the device. Handles special characters by converting spaces to %s and escaping shell metacharacters. For multi-line or complex text, consider using the clipboard tool instead.
This record as markdown: /tools/io-github-fullread-deepadb/adb-input-text.md
What adb_input_text does on Deepadb
AI agents invoke adb_input_text to trigger actions in Deepadb. 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.
Why adb_input_text is rated High
This tool executes ADB shell input commands to type text on a connected Android device. It has real side effects (filling forms, triggering actions based on typed text), involves shell metacharacter escaping (indicating direct shell execution), and can affect whatever the current focused element is.
From the tool's definition 'Type text on the device' and 'converting spaces to %s and escaping shell metacharacters' — triggers ADB input commands that send keystrokes to the active UI element on a remote device
Attacks that exploit this kind of access
The rule that runs adb_input_text safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_input_text, this is the rule to start with:
adb_input_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_input_text call is checked against it from then on.
Questions about adb_input_text
Type text on the device. Handles special characters by converting spaces to %s and escaping shell metacharacters. For multi-line or complex text, consider using the clipboard tool instead. It is categorised as a Execute tool in the Deepadb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_input_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 Deepadb. Nothing to install.
adb_input_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 adb_input_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 adb_input_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.
adb_input_text is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadb, and thousands of servers like it.
Across the catalogue