list_conflicts

SERVERMegaMemory SOURCE0xk3vin/megamemory

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

WHAT IT DOES

What list_conflicts does on MegaMemory

AI agents call list_conflicts to retrieve information from MegaMemory without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_conflicts is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_conflicts safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MegaMemory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_conflicts, this is the rule to start with:

list_conflicts Allowed

list_conflicts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_conflicts": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MegaMemory, apply this rule, and every list_conflicts call is checked against it from then on.

FAQ

Questions about list_conflicts

What does the list_conflicts tool do? +

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.

How do I enforce a policy on list_conflicts? +

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.

What risk level is list_conflicts? +

list_conflicts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_conflicts? +

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.

How do I block list_conflicts completely? +

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.

What MCP server provides list_conflicts? +

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.

KEEP EXPLORING

More on MegaMemory, and thousands of servers like it.

This server

All 9 MegaMemory tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →