Set clipboard content.
AI agents use cond_clipboard_set to create or update resources in TermPipe MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TermPipe MCP environment.
This tool creates or modifies data (clipboard content) without permanent deletion or irreversible side effects. While it affects system state, clipboard modifications are easily overwritten and pose minimal risk. It does not execute arbitrary commands, delete data, or commit financial transactions. The conditional prefix ('cond_') suggests it may have guard conditions, further reducing risk.
From the tool's definition Tool name is 'cond_clipboard_set' and description states 'Set clipboard content.' The action modifies the clipboard state, which is a reversible write operation.
Attacks that exploit this kind of access
Set clipboard content. It is categorised as a Write tool in the TermPipe MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TermPipe MCP server in PolicyLayer and add a rule for cond_clipboard_set: 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 TermPipe MCP. Nothing to install.
cond_clipboard_set 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 cond_clipboard_set 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 cond_clipboard_set. 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.
cond_clipboard_set is provided by the TermPipe MCP server (wbind-core/termpipe-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 →