List memory conflicts (contradictions) that need resolution. Conflicts are detected when the memory system finds contradictory information, such as two memories stating different facts about the same entity. Args: status: Filter by status ('open', 'resolved', 'dismissed'). Default shows all. limi...
AI agents call conflict_list to retrieve information from Yantrikdb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing memory conflict data without side effects. It reads contradictions already detected by the memory system and returns structured information. No data is created, modified, deleted, or executed. The severity is low because listing conflicts poses minimal risk—it's purely informational and supports transparency in the cognitive memory system.
From the tool's definition Tool description explicitly states 'List memory conflicts' and returns conflicts with metadata. The only verbs are 'List' and 'detect', with no modifications, deletions, or executions. Args are filtering parameters (status, limit), not actions.
Documented attack patterns abuse exactly the kind of access conflict_list 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_list:
{
"version": "1",
"default": "deny",
"tools": {
"conflict_list": {}
}
}conflict_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List memory conflicts (contradictions) that need resolution. Conflicts are detected when the memory system finds contradictory information, such as two memories stating different facts about the same entity. Args: status: Filter by status ('open', 'resolved', 'dismissed'). Default shows all. limit: Maximum number of conflicts to return (default 10). Returns conflicts with their IDs, types, priorities, and the conflicting memories. It is categorised as a Read tool in the Yantrikdb MCP Server, which means it retrieves data without modifying state.
Register the Yantrikdb MCP server in PolicyLayer and add a rule for conflict_list: 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_list 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 conflict_list 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_list. 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_list 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.