Track, search, and restore clipboard history across sessions. Maintains up to 100 entries in ~/.pilotgentic/clipboard-history.json.
AI agents call pilotgentic_clipboard_history to retrieve information from PilotGentic without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The primary operations are tracking, searching, and restoring (reading) clipboard history. While 'restore' could imply modification, the context indicates viewing/retrieving historical clipboard entries rather than destructive alteration. However, medium severity is assigned because clipboard history often contains sensitive data (passwords, tokens, PII, API keys) that an agent could exfiltrate through read access.
From the tool's definition Tool description states it "Track, search, and restore clipboard history" — these are read operations. The tool accesses and queries stored clipboard data in ~/.pilotgentic/clipboard-history.json but does not modify or delete entries based on the description…
Attacks that exploit this kind of access
Track, search, and restore clipboard history across sessions. Maintains up to 100 entries in ~/.pilotgentic/clipboard-history.json. It is categorised as a Read tool in the PilotGentic MCP Server, which means it retrieves data without modifying state.
Register the PilotGentic MCP server in PolicyLayer and add a rule for pilotgentic_clipboard_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 PilotGentic. Nothing to install.
pilotgentic_clipboard_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 pilotgentic_clipboard_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 pilotgentic_clipboard_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.
pilotgentic_clipboard_history is provided by the PilotGentic MCP server (@pilotgentic/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 →