New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

record_conflict_decision

Records an operator's manual decision for a conflict pair.

SERVERMapi Agent Memory SOURCEcabo0m/mapi-agent-memory
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about record_conflict_decision

What does the record_conflict_decision tool do? +

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.

How do I enforce a policy on record_conflict_decision? +

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.

What risk level is record_conflict_decision? +

record_conflict_decision is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit record_conflict_decision? +

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.

How do I block record_conflict_decision completely? +

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.

What MCP server provides record_conflict_decision? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mapi Agent Memory's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.