Cancel a pending reminder. Caller must own the reminder.
AI agents call memory_cancel_reminder to permanently remove resources in Junto Memory — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call memory_cancel_reminder doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Junto Memory is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Cancel a pending reminder. Caller must own the reminder. It is categorised as a Destructive tool in the Junto Memory MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Junto Memory MCP server in PolicyLayer and add a rule for memory_cancel_reminder: 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 Junto Memory. Nothing to install.
memory_cancel_reminder is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the memory_cancel_reminder 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 memory_cancel_reminder. 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.
memory_cancel_reminder is provided by the Junto Memory MCP server (tlemmons/junto-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.