reject_memory
A write tool on the Mapi Agent Memory MCP server.
This record as markdown: /tools/mapi-agent-memory/reject-memory.md
What reject_memory does on Mapi Agent Memory
AI agents use reject_memory 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.
Why reject_memory is rated Medium
The tool appears to reject or invalidate memory entries, which constitutes a write/modification operation that changes agent memory state. This is categorized as Write rather than Destructive because rejection of memory typically marks it as invalid rather than permanently deleting underlying data.
From the tool's definition Tool name 'reject_memory' suggests modification of memory state; context from sibling tools (apply_approved_memory_consolidation_proposal, apply_conflict_resolution, apply_escalation_reactions) indicates this server manages agent memory governance with…
Attacks that exploit this kind of access
The rule that runs reject_memory 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, this is the rule to start with:
reject_memory 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mapi Agent Memory, apply this rule, and every reject_memory call is checked against it from then on.
Questions about reject_memory
reject_memory is a write tool on the Mapi Agent Memory MCP server. 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.
Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for reject_memory: 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.
reject_memory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reject_memory 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 reject_memory. 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.
reject_memory 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