Resolve a memory conflict using a strategy. Args: conflict_id: The conflict ID to resolve. strategy: One of 'keep_a' (keep memory A), 'keep_b' (keep memory B), 'keep_both' (keep both, mark as non-conflicting), 'merge' (combine into one). winner_rid: For keep_a/keep_b, which memory wins (optional,...
AI agents use conflict_resolve to create or update resources in Yantrikdb — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yantrikdb environment.
The tool creates or modifies data (memory conflicts) through resolution operations. While it doesn't delete (which would be Destructive), it rewrites memory state based on chosen strategies, including merging or selecting between conflicting records. This is a reversible Write operation.
From the tool's definition Tool modifies memory state through strategies like 'keep_a', 'keep_b', 'keep_both', 'merge', and accepts 'new_text' parameter for merged content. These operations reversibly update stored memory records.
Documented attack patterns abuse exactly the kind of access conflict_resolve gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Yantrikdb, and nothing reaches the server without passing your rules. This is the rule we recommend for conflict_resolve:
{
"version": "1",
"default": "deny",
"tools": {
"conflict_resolve": {
"limits": [
{
"counter": "conflict_resolve_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}conflict_resolve 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.
Resolve a memory conflict using a strategy. Args: conflict_id: The conflict ID to resolve. strategy: One of 'keep_a' (keep memory A), 'keep_b' (keep memory B), 'keep_both' (keep both, mark as non-conflicting), 'merge' (combine into one). winner_rid: For keep_a/keep_b, which memory wins (optional, inferred from strategy). new_text: For 'merge' strategy, the merged text content. resolution_note: Optional note explaining the resolution. Returns the resolution result. It is categorised as a Write tool in the Yantrikdb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Yantrikdb MCP server in PolicyLayer and add a rule for conflict_resolve: 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 Yantrikdb. Nothing to install.
conflict_resolve 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 conflict_resolve 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 conflict_resolve. 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.
conflict_resolve is provided by the Yantrikdb MCP server (yantrikos/yantrikdb-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Yantrikdb tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Yantrikdb tools catalogued and risk-classified — across an index of 42,500+ MCP servers.