AI agents use set_clipboard to create or update resources in Mac — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mac environment.
This tool modifies data (clipboard content) but the operation is reversible - new clipboard content can be set again. It does not execute code, delete data, or move money.
From the tool's definition Tool description explicitly states it 'Sets clipboard to specified text content' - a write operation that modifies system state (clipboard content) reversibly.
Attacks that exploit this kind of access
Sets clipboard to specified text content. It is categorised as a Write tool in the Mac MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mac MCP server in PolicyLayer and add a rule for set_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 Mac. Nothing to install.
set_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_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_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_clipboard is provided by the Mac MCP server (laststance/mac-mcp-server). 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 →