reject_memory_consolidation_proposal

Reject a consolidation proposal by changing review-state only.

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/reject-memory-consolidation-proposal.md

WHAT IT DOES

What reject_memory_consolidation_proposal does on Mapi Agent Memory

AI agents use reject_memory_consolidation_proposal 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.

RISK

Why reject_memory_consolidation_proposal is rated Medium

This tool modifies the state of a memory consolidation proposal (from pending/proposed to rejected), which is a write operation. It does not delete data (would be Destructive), does not execute external operations (would be Execute), and does not move money (would be Financial).

From the tool's definition Tool description states it changes review-state, which modifies data. The word 'Reject' combined with 'changing review-state only' indicates a reversible state transition rather than deletion or approval execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

reject_memory_consolidation_proposal Rate-limited

reject_memory_consolidation_proposal stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reject_memory_consolidation_proposal": {
      "limits": [
        {
          "counter": "reject_memory_consolidation_proposal_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about reject_memory_consolidation_proposal

What does the reject_memory_consolidation_proposal tool do? +

Reject a consolidation proposal by changing review-state only. 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 reject_memory_consolidation_proposal? +

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

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

Can I rate-limit reject_memory_consolidation_proposal? +

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

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

reject_memory_consolidation_proposal 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

team_manager_write_memory on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →