record_conflict_decision
Records an operator's manual decision for a conflict pair.
This record as markdown: /tools/mapi-agent-memory/record-conflict-decision.md
What record_conflict_decision does on Mapi Agent Memory
AI agents use record_conflict_decision to create or update resources in Mapi Agent Memory, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mapi Agent Memory environment.
Why record_conflict_decision is rated Medium
This tool writes/stores a decision record for a conflict pair. It creates or modifies data (the conflict resolution record) in a reversible manner. It does not delete data, execute code, or involve financial transactions. Misuse could corrupt governance audit trails, hence medium severity.
From the tool's definition Records an operator's manual decision for a conflict pair
Attacks that exploit this kind of access
The rule that runs record_conflict_decision 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 record_conflict_decision, this is the rule to start with:
record_conflict_decision stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 record_conflict_decision call is checked against it from then on.
Questions about record_conflict_decision
Records an operator's manual decision for a conflict pair. It is categorised as a Write tool in the Mapi Agent Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for record_conflict_decision: 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.
record_conflict_decision is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the record_conflict_decision 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 record_conflict_decision. 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.
record_conflict_decision 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