AI agents use copy_to_clipboard to create or update resources in MCP System Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP System Bridge environment.
This tool modifies the clipboard (a system resource) by writing text to it, but the operation is completely reversible—new content can overwrite it immediately. It has no external side effects, doesn't execute code, and poses minimal risk even if misused. The main concern would be replacing sensitive data a user intended to paste, but this is a low-severity issue with limited blast radius.
From the tool's definition 'Copy text to the clipboard' is a data modification operation that creates/updates clipboard state, fitting the Write category definition of 'creates or modifies data reversibly'.
Documented attack patterns abuse exactly the kind of access copy_to_clipboard gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP System Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for copy_to_clipboard:
{
"version": "1",
"default": "deny",
"tools": {
"copy_to_clipboard": {
"limits": [
{
"counter": "copy_to_clipboard_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}copy_to_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.
Copy text to the clipboard. It is categorised as a Write tool in the MCP System Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP System Bridge 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 MCP System Bridge. 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 MCP System Bridge MCP server (leynier/mcp-sys-bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP System Bridge, 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.
4 MCP System Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.