get_conflict_registry
Return a registry-style view of conflict clusters with lifecycle status.
This record as markdown: /tools/mapi-agent-memory/get-conflict-registry.md
What get_conflict_registry does on Mapi Agent Memory
AI agents call get_conflict_registry to retrieve information from Mapi Agent Memory without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_conflict_registry is rated Low
This tool queries and returns information about conflict clusters and their lifecycle status without creating, modifying, deleting, or executing any operations. It is a passive retrieval operation that has no side effects on the system state. The low severity reflects that unauthorized access would only expose metadata about conflicts rather than enable destructive or financial actions.
From the tool's definition Tool name 'get_conflict_registry' and description 'Return a registry-style view of conflict clusters with lifecycle status' indicate data retrieval without modification. The verb 'Return' and 'view' are passive operations characteristic of Read category tools.
Attacks that exploit this kind of access
The rule that runs get_conflict_registry safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mapi Agent Memory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_conflict_registry, this is the rule to start with:
get_conflict_registry is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mapi Agent Memory, apply this rule, and every get_conflict_registry call is checked against it from then on.
Questions about get_conflict_registry
Return a registry-style view of conflict clusters with lifecycle status. It is categorised as a Read tool in the Mapi Agent Memory MCP Server, which means it retrieves data without modifying state.
Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for get_conflict_registry: 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 Mapi Agent Memory. Nothing to install.
get_conflict_registry 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 get_conflict_registry 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 get_conflict_registry. 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.
get_conflict_registry is provided by the Mapi Agent Memory MCP server (cabo0m/mapi-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mapi Agent Memory, and thousands of servers like it.
This server
Across the catalogue