get_conflict_quality_metrics
Returns quality metrics for the conflict explainer subsystem.
This record as markdown: /tools/mapi-agent-memory/get-conflict-quality-metrics.md
What get_conflict_quality_metrics does on Mapi Agent Memory
AI agents call get_conflict_quality_metrics 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_quality_metrics is rated Low
This tool queries and retrieves metrics about the conflict explainer subsystem. The verb 'Returns' and lack of any modification, execution, or destructive capability clearly place it in the Read category. The blast radius is minimal: misuse would only expose internal metrics, not alter state or trigger external actions. Confidence is high because the description is explicit about the retrieval nature.
From the tool's definition Tool name and description indicate it 'Returns quality metrics' — a retrieval operation with no side effects or data modification.
Attacks that exploit this kind of access
The rule that runs get_conflict_quality_metrics 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_quality_metrics, this is the rule to start with:
get_conflict_quality_metrics 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_quality_metrics call is checked against it from then on.
Questions about get_conflict_quality_metrics
Returns quality metrics for the conflict explainer subsystem. 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_quality_metrics: 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_quality_metrics 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_quality_metrics 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_quality_metrics. 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_quality_metrics 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