AI agents use write_clipboard to create or update resources in uiautomator2 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your uiautomator2 MCP Server environment.
Writing to clipboard modifies device state reversibly and could be used to inject malicious content, credentials, or commands into applications that read from clipboard. This is a Write operation (reversible modification) rather than Read-only.
From the tool's definition Tool name 'write_clipboard' indicates it writes data to the device's clipboard. While the description is empty, the name and context of an Android automation tool clearly indicates clipboard mutation.
Documented attack patterns abuse exactly the kind of access write_clipboard 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 write_clipboard:
{
"version": "1",
"default": "deny",
"tools": {
"write_clipboard": {
"limits": [
{
"counter": "write_clipboard_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}write_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.
Free to start. No card required.
write_clipboard. It is categorised as a Write tool in the uiautomator2 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the uiautomator2 MCP Server MCP server in PolicyLayer and add a rule for write_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 uiautomator2 MCP Server. Nothing to install.
write_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 write_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 write_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.
write_clipboard 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.