Clear clipboard history.
AI agents call clipboard_history_clear to permanently remove resources in Android MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible action that destroys data (clipboard history) and cannot be undone. The 'clear' operation is inherently destructive. While the data involved (clipboard history) is typically non-critical, the irreversible nature and lack of recovery mechanism classify it as Destructive rather than Write.
From the tool's definition The tool name explicitly includes 'clear' which is an irreversible deletion operation. The description 'Clear clipboard history' indicates the tool permanently removes all clipboard history records from the device.
Attacks that exploit this kind of access
Clear clipboard history. It is categorised as a Destructive tool in the Android MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Android MCP Server MCP server in PolicyLayer and add a rule for clipboard_history_clear: 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 Android MCP Server. Nothing to install.
clipboard_history_clear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clipboard_history_clear 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 clipboard_history_clear. 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.
clipboard_history_clear is provided by the Android MCP Server MCP server (wujie272/android-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →