Clear old completed/moved reminders
AI agents call clear_old_reminders to permanently remove resources in MCP Reminders — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs a permanent deletion operation (clear) on past reminder data. While the severity is low because reminders are non-critical data with minimal blast radius, the action is irreversible and therefore falls under the Destructive category rather than Write. An AI agent could accidentally purge important reminder history, but recovery would be limited to backups outside the tool's scope.
From the tool's definition Tool name 'clear_old_reminders' and description 'Clear old completed/moved reminders' indicate irreversible deletion of reminder records.
Attacks that exploit this kind of access
Clear old completed/moved reminders. It is categorised as a Destructive tool in the MCP Reminders MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Reminders MCP server in PolicyLayer and add a rule for clear_old_reminders: 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 MCP Reminders. Nothing to install.
clear_old_reminders 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 clear_old_reminders 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 clear_old_reminders. 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.
clear_old_reminders is provided by the MCP Reminders MCP server (mikeybeez/mcp-reminders). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →