Push local knowledge entries and session summaries to the cloud server. Only pushes entries newer than the last sync.
AI agents use cloud_sync_push to create or update resources in ClaudeHistoryMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ClaudeHistoryMCP environment.
This tool falls under Write because it creates or uploads data to a cloud backend. While the blast radius is moderate (could upload sensitive session history or corrupted summaries), it is not Destructive (data is not irreversibly deleted), not Execute (no code execution or external operations triggered), and not Financial.
From the tool's definition Tool performs 'Push local knowledge entries and session summaries to the cloud server', which creates or modifies data on a remote system.
Documented attack patterns abuse exactly the kind of access cloud_sync_push gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ClaudeHistoryMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for cloud_sync_push:
{
"version": "1",
"default": "deny",
"tools": {
"cloud_sync_push": {
"limits": [
{
"counter": "cloud_sync_push_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}cloud_sync_push 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.
Push local knowledge entries and session summaries to the cloud server. Only pushes entries newer than the last sync. It is categorised as a Write tool in the ClaudeHistoryMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ClaudeHistory MCP server in PolicyLayer and add a rule for cloud_sync_push: 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 ClaudeHistoryMCP. Nothing to install.
cloud_sync_push 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 cloud_sync_push 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 cloud_sync_push. 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.
cloud_sync_push is provided by the ClaudeHistory MCP server (jhammant/claudehistorymcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ClaudeHistoryMCP, 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.
9 ClaudeHistoryMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.