Retrieve operation history for debugging
AI agents call get_operation_history to retrieve information from Cut-Copy-Paste Clipboard Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical data about clipboard operations for auditing and debugging purposes. It performs no modifications, deletions, or external triggering—purely a data retrieval function. The operation history is immutable historical metadata, making this a straightforward Read category with low severity.
From the tool's definition Tool name 'get_operation_history' and description 'Retrieve operation history for debugging' indicate a read-only query operation with no side effects.
Attacks that exploit this kind of access
Retrieve operation history for debugging. It is categorised as a Read tool in the Cut-Copy-Paste Clipboard Server MCP Server, which means it retrieves data without modifying state.
Register the Cut-Copy-Paste Clipboard Server MCP server in PolicyLayer and add a rule for get_operation_history: 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 Cut-Copy-Paste Clipboard Server. Nothing to install.
get_operation_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_operation_history 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 get_operation_history. 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.
get_operation_history is provided by the Cut-Copy-Paste Clipboard Server MCP server (pr0j3c7t0dd-ltd/cut-copy-paste-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 →