list_review_events

A read tool on the Mapi Agent Memory MCP server.

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/list-review-events.md

WHAT IT DOES

What list_review_events does on Mapi Agent Memory

AI agents call list_review_events 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 list_review_events is rated Low

The 'list_' prefix is a clear indicator of a read operation that retrieves or queries existing review events without modification. Given the governance and auditing context of the server, this tool likely returns historical records or status information.

From the tool's definition Tool name is 'list_review_events' which follows the read pattern (list, get, fetch). The empty description prevents higher confidence, but the sibling tools on this memory governance server consistently show operational separation between read operations…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_review_events Allowed

list_review_events 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": {
    "list_review_events": {}
  }
}

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 list_review_events call is checked against it from then on.

FAQ

Questions about list_review_events

What does the list_review_events tool do? +

list_review_events is a read tool on the Mapi Agent Memory MCP server. 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 list_review_events? +

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

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

Can I rate-limit list_review_events? +

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

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

list_review_events 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

review_changes on MCP Server PR Pilot →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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