compare_memory_modes

Compare classic retrieval output with v2 restore/project-card output on the same scenario.

SERVERMapi Agent Memory SOURCEcabo0m/mapi-agent-memory

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mapi-agent-memory/compare-memory-modes.md

WHAT IT DOES

What compare_memory_modes does on Mapi Agent Memory

AI agents call compare_memory_modes 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.

RISK

Why compare_memory_modes is rated Low

The tool performs a comparison of two output modes from the same system, retrieving and presenting data side-by-side for analysis. This is fundamentally a read operation that queries existing memory modes without creating, modifying, or deleting data. No side effects or irreversible changes are possible.

From the tool's definition Tool description states it "compare[s]" classic retrieval output with v2 restore/project-card output on the same scenario. This is a data retrieval and comparison operation with no modification, deletion, or execution of external code.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs compare_memory_modes 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 compare_memory_modes, this is the rule to start with:

compare_memory_modes Allowed

compare_memory_modes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "compare_memory_modes": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mapi Agent Memory, apply this rule, and every compare_memory_modes call is checked against it from then on.

FAQ

Questions about compare_memory_modes

What does the compare_memory_modes tool do? +

Compare classic retrieval output with v2 restore/project-card output on the same scenario. It is categorised as a Read tool in the Mapi Agent Memory MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on compare_memory_modes? +

Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for compare_memory_modes: 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 compare_memory_modes? +

compare_memory_modes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit compare_memory_modes? +

Yes. Add a rate_limit block to the compare_memory_modes 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 compare_memory_modes completely? +

Set action: deny in the PolicyLayer policy for compare_memory_modes. 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 compare_memory_modes? +

compare_memory_modes 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.

KEEP EXPLORING

More on Mapi Agent Memory, and thousands of servers like it.

This server

All 252 Mapi Agent Memory tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →