mcp_read
AI agents call mcp_read to retrieve information from MCP CopyQ Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and server context indicate this retrieves clipboard data without modification. Empty description lowers confidence slightly, but the naming convention (mcp_read) and server's stated capability to support 'reading' clipboard items clearly positions this as a Read operation. Severity is low as it only accesses user clipboard data without side effects or privilege escalation risk.
From the tool's definition Tool name 'mcp_read' and server description indicating 'reading...clipboard items organized in tabs with tags and notes through a unified interface.'
Attacks that exploit this kind of access
mcp_read. It is categorised as a Read tool in the MCP CopyQ Server MCP Server, which means it retrieves data without modifying state.
Register the MCP CopyQ Server MCP server in PolicyLayer and add a rule for mcp_read: 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 CopyQ Server. Nothing to install.
mcp_read 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 mcp_read 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 mcp_read. 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.
mcp_read is provided by the MCP CopyQ Server MCP server (list91/mcp-copyq). 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 →