Compute a stateless 3-way merge for a vault file. Server runs git merge-file --diff3 --stdout over (base_text, local_text, current remote from file_indices) and returns the merged text plus the exact remote_sha it merged against. NO database mutation — to commit the result, follow up with sync_pu...
Risk signalsAccepts file system path (path)
Part of the Ainote server.
Free to start. No card required.
AI agents use sync_merge to create or modify resources in Ainote. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call sync_merge repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Ainote.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"sync_merge": {
"limits": [
{
"counter": "sync_merge_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Ainote policy for all 32 tools.
These attack patterns abuse exactly the kind of access sync_merge gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Compute a stateless 3-way merge for a vault file. Server runs git merge-file --diff3 --stdout over (base_text, local_text, current remote from file_indices) and returns the merged text plus the exact remote_sha it merged against. NO database mutation — to commit the result, follow up with sync_push(content=merged_text, base_sha=merged_against.remote_sha, resolves_conflict_id=conflict_id).. It is categorised as a Write tool in the Ainote MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ainote MCP server in PolicyLayer and add a rule for sync_merge: 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 Ainote. Nothing to install.
sync_merge 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 sync_merge 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 sync_merge. 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.
sync_merge is provided by the Ainote MCP server (@ainote/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 32 Ainote tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.