copy data to clipboard
AI agents use copy_to_clipboard to create or update resources in Macos Clipboard — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Macos Clipboard environment.
This tool writes data to the clipboard, which is a reversible operation with minimal side effects. The data persists only in clipboard memory until overwritten or cleared. There is no data destruction, financial impact, or code execution involved. Severity is low because clipboard modifications have limited blast radius and do not affect persistent system state or user data beyond the temporary clipboard buffer.
From the tool's definition Tool description states 'copy data to clipboard' which modifies clipboard state. Server description confirms it uses AppleScript to copy text to macOS clipboard.
Attacks that exploit this kind of access
copy data to clipboard. It is categorised as a Write tool in the Macos Clipboard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Macos Clipboard MCP server in PolicyLayer and add a rule for copy_to_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 Macos Clipboard. Nothing to install.
copy_to_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 copy_to_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 copy_to_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.
copy_to_clipboard is provided by the Macos Clipboard MCP server (xiaoquisme/macos-cliboard-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 →