List all unresolved merge conflicts in the knowledge graph, grouped by merge_group. Each group contains competing versions with full data. Call this when the user runs /merge to begin AI-assisted conflict resolution.
AI agents call list_conflicts to retrieve information from MegaMemory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing conflict information without creating, modifying, deleting, or executing any operations. It is purely informational, helping users understand the state of the knowledge graph before conflict resolution. The most severe action it enables is reading conflict metadata, making it a Read category tool with low severity due to its passive, non-destructive nature.
From the tool's definition 'List all unresolved merge conflicts' is a query operation that retrieves conflict data from the knowledge graph without modification or side effects. The description explicitly states it lists conflicts and provides 'full data' for review.
Documented attack patterns abuse exactly the kind of access list_conflicts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MegaMemory, and nothing reaches the server without passing your rules. This is the rule we recommend for list_conflicts:
{
"version": "1",
"default": "deny",
"tools": {
"list_conflicts": {}
}
}list_conflicts 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 all unresolved merge conflicts in the knowledge graph, grouped by merge_group. Each group contains competing versions with full data. Call this when the user runs /merge to begin AI-assisted conflict resolution. It is categorised as a Read tool in the MegaMemory MCP Server, which means it retrieves data without modifying state.
Register the MegaMemory MCP server in PolicyLayer and add a rule for list_conflicts: 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 MegaMemory. Nothing to install.
list_conflicts 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 list_conflicts 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 list_conflicts. 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.
list_conflicts is provided by the MegaMemory MCP server (0xk3vin/megamemory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 MegaMemory tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 MegaMemory tools catalogued and risk-classified — across an index of 42,500+ MCP servers.