adb_clipboard
Read or write the device clipboard. Write mode sets the clipboard content; read mode retrieves it. Clipboard access requires Android 10+ and may need the app to be in foreground on Android 12+.
This record as markdown: /tools/io-github-fullread-deepadb/adb-clipboard.md
What adb_clipboard does on Deepadb
AI agents use adb_clipboard to create or update resources in Deepadb, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Deepadb environment.
Why adb_clipboard is rated Medium
Clipboard write access is a Write operation that modifies device state. It reaches high severity because a compromised agent could inject malicious content (URLs, commands, credentials) into the clipboard for a user to unknowingly paste, enabling credential theft, phishing, or command injection attacks.
From the tool's definition Tool description explicitly states it can 'Write...the device clipboard' and 'sets the clipboard content'. While it also reads clipboard, the ability to write/modify clipboard content is the primary distinguishing capability.
Attacks that exploit this kind of access
The rule that runs adb_clipboard 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_clipboard, this is the rule to start with:
adb_clipboard stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_clipboard call is checked against it from then on.
Questions about adb_clipboard
Read or write the device clipboard. Write mode sets the clipboard content; read mode retrieves it. Clipboard access requires Android 10+ and may need the app to be in foreground on Android 12+. It is categorised as a Write tool in the Deepadb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_clipboard: 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_clipboard is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the adb_clipboard 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_clipboard. 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_clipboard 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.
This server
Across the catalogue