Set clipboard content on Android device
AI agents use set_android_clipboard to create or update resources in MCP Prompts Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Prompts Server environment.
Setting clipboard content is a reversible write operation that alters device state. While not destructive (clipboard can be overwritten), it has medium severity because an attacker could exfiltrate sensitive data by replacing clipboard contents with malicious content, or inject credentials/commands into workflows that paste from clipboard.
From the tool's definition Tool description states 'Set clipboard content on Android device' — this modifies device state by writing to a protected system resource.
Documented attack patterns abuse exactly the kind of access set_android_clipboard gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Prompts Server, and nothing reaches the server without passing your rules. This is the rule we recommend for set_android_clipboard:
{
"version": "1",
"default": "deny",
"tools": {
"set_android_clipboard": {
"limits": [
{
"counter": "set_android_clipboard_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_android_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.
Set clipboard content on Android device. It is categorised as a Write tool in the MCP Prompts Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Prompts Server MCP server in PolicyLayer and add a rule for set_android_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 MCP Prompts Server. Nothing to install.
set_android_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 set_android_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 set_android_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.
set_android_clipboard is provided by the MCP Prompts Server MCP server (sparesparrow/mcp-prompts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 51 MCP Prompts Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
51 MCP Prompts Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.