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

get_memory_consolidation_lifecycle_report

Return a read-only lifecycle report for consolidation proposals and their apply/rollback audit chain.

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/get-memory-consolidation-lifecycle-report.md

What get_memory_consolidation_lifecycle_report does on Mapi Agent Memory

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

This tool only queries and returns audit data about memory consolidation proposals and their historical lifecycle. The 'read-only' designation and focus on reporting (not application or modification) clearly places it in the Read category. Even though it operates on sensitive governance/audit data, the lack of ability to modify state, execute operations, or cause side effects keeps severity low.

From the tool's definition Tool description explicitly states 'Return a read-only lifecycle report' with no modification capability mentioned. It retrieves audit chain and consolidation proposal status without side effects.

Questions about get_memory_consolidation_lifecycle_report

What does the get_memory_consolidation_lifecycle_report tool do? +

Return a read-only lifecycle report for consolidation proposals and their apply/rollback audit chain. 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 get_memory_consolidation_lifecycle_report? +

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

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

Can I rate-limit get_memory_consolidation_lifecycle_report? +

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

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

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