AI agents use export_history to create or update resources in Maccy Clipboard MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Maccy Clipboard MCP environment.
This tool writes clipboard history data to persistent storage (a local file). While the operation is reversible (the file can be deleted or overwritten), it involves creating or modifying files on the user's system. This is a Write operation rather than Read (since it modifies the filesystem) or Destructive (since exporting is reversible).
From the tool's definition Tool description: 'Export clipboard history to a local file'. The tool creates a new file containing clipboard history data, which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access export_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Maccy Clipboard MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for export_history:
{
"version": "1",
"default": "deny",
"tools": {
"export_history": {
"limits": [
{
"counter": "export_history_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_history 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.
Export clipboard history to a local file. It is categorised as a Write tool in the Maccy Clipboard MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Maccy Clipboard MCP server in PolicyLayer and add a rule for export_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 Maccy Clipboard MCP. Nothing to install.
export_history 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 export_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 export_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.
export_history is provided by the Maccy Clipboard MCP server (vlad-ds/maccy-clipboard-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Maccy Clipboard MCP, 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.
8 Maccy Clipboard MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.