delete_reminder_list

Deletes an Apple Reminders list AND all reminders inside it — cannot be undone. Pass the list name (or list_id from list_reminder_lists). Requires confirm=true.

SERVERLocal SOURCElocal-mcp
Critical RISK CLASS
Category Destructive
Parameters 30 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/delete-reminder-list.md

What delete_reminder_list does on Local

AI agents call delete_reminder_list to permanently remove resources in Local, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
name string List name to delete (or pass list_id)
confirm boolean Must be true to delete
list_id string List identifier from list_reminder_lists (alternative to name)

Parameters from the server's own tool schema.

Why delete_reminder_list is rated Critical

This tool irreversibly deletes both a reminders list and all its contents with no undo capability. While it requires explicit confirmation (confirm=true) to mitigate accidental misuse, the destructive nature—permanent removal of user data—places it in the Destructive category rather than Write.

From the tool's definition Tool description explicitly states 'Deletes an Apple Reminders list AND all reminders inside it — cannot be undone.' The verb 'deletes' combined with 'cannot be undone' is the defining characteristic of destructive operations.

Questions about delete_reminder_list

What does the delete_reminder_list tool do? +

Deletes an Apple Reminders list AND all reminders inside it — cannot be undone. Pass the list name (or list_id from list_reminder_lists). Requires confirm=true. It is categorised as a Destructive tool in the Local MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does delete_reminder_list accept? +

delete_reminder_list accepts 3 parameters: name, confirm, list_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on delete_reminder_list? +

Register the Local MCP server in PolicyLayer and add a rule for delete_reminder_list: 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 Local. Nothing to install.

What risk level is delete_reminder_list? +

delete_reminder_list is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_reminder_list? +

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

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

delete_reminder_list is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Local, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Local's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.