rename_reminder_list

Renames an existing Apple Reminders list. Pass the current list name (or list_id from list_reminder_lists) and new_name. Requires confirm=true.

SERVERLocal SOURCElocal-mcp

Medium RISK CLASS

Category Write

Parameters 41 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What rename_reminder_list does on Local

AI agents use rename_reminder_list to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.

Parameter	Type	Required	Description
`name`	string	—	Current list name (or pass list_id)
`confirm`	boolean	—	Must be true to apply
`list_id`	string	—	List identifier from list_reminder_lists (alternative to name)
`new_name`	string	Yes	New name for the list

Parameters from the server's own tool schema.

RISK

Why rename_reminder_list is rated Medium

Renaming a reminder list is a reversible write operation that modifies metadata but does not delete or execute code. The requirement for confirm=true mitigates severity slightly, but this remains a data modification (Write category).

From the tool's definition The tool 'renames an existing Apple Reminders list' by accepting a current name/ID and new_name parameter. This is a modification operation that changes data state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs rename_reminder_list safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rename_reminder_list, this is the rule to start with:

rename_reminder_list Rate-limited

rename_reminder_list 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename_reminder_list": {
      "limits": [
        {
          "counter": "rename_reminder_list_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every rename_reminder_list call is checked against it from then on.

FAQ

Questions about rename_reminder_list

What does the rename_reminder_list tool do? +

Renames an existing Apple Reminders list. Pass the current list name (or list_id from list_reminder_lists) and new_name. Requires confirm=true. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does rename_reminder_list accept? +

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

How do I enforce a policy on rename_reminder_list? +

Register the Local MCP server in PolicyLayer and add a rule for rename_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 rename_reminder_list? +

rename_reminder_list is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rename_reminder_list? +

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

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

rename_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.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →