Delete a reminder. This action cannot be undone.
AI agents call delete_reminder to permanently remove resources in Reminders MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes reminder records from the macOS Reminders app without reversibility. Although the blast radius is confined to personal reminder data (not system-critical or financial), the irreversible nature and explicit 'cannot be undone' warning classify this as Destructive rather than Write. Confidence is high due to clear naming and description.
From the tool's definition Tool name 'delete_reminder' combined with description 'This action cannot be undone' explicitly indicates irreversible deletion of data.
Attacks that exploit this kind of access
Delete a reminder. This action cannot be undone. It is categorised as a Destructive tool in the Reminders MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Reminders MCP Server MCP server in PolicyLayer and add a rule for delete_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 Reminders MCP Server. Nothing to install.
delete_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 delete_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 delete_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.
delete_reminder is provided by the Reminders MCP Server MCP server (jagadeesh52423/remainders-mcp). 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 →