Find conflicting memories.
AI agents call memory_conflicts to retrieve information from Rekal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches or queries existing memories to detect conflicts—a retrieval task with no side effects. It does not create, modify, delete, or execute external operations. The blast radius of misuse is minimal; the worst outcome would be incorrect conflict detection results, not data loss or unauthorized actions.
From the tool's definition Tool name 'memory_conflicts' and description 'Find conflicting memories' indicate a query/search operation that retrieves and identifies conflicting data from the local SQLite memory store.
Documented attack patterns abuse exactly the kind of access memory_conflicts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rekal, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_conflicts:
{
"version": "1",
"default": "deny",
"tools": {
"memory_conflicts": {}
}
}memory_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.
Find conflicting memories. It is categorised as a Read tool in the Rekal MCP Server, which means it retrieves data without modifying state.
Register the Rekal MCP server in PolicyLayer and add a rule for memory_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 Rekal. Nothing to install.
memory_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 memory_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 memory_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.
memory_conflicts is provided by the Rekal MCP server (janbjorge/rekal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rekal, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Rekal tools catalogued and risk-classified — across an index of 43,000+ MCP servers.