rename_reminder_list · Reminders MCP Server MCP

WHAT IT DOES

What rename_reminder_list does on Reminders MCP Server

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

WHY IT NEEDS A POLICY

Why rename_reminder_list needs a policy

Renaming a reminder list is a metadata modification that changes a property of existing data. This is a Write operation: it creates or modifies data reversibly. While the severity is low because renaming has minimal blast radius (the list and its reminders remain intact and functional), it qualifies as Write rather than Read (which would be get_reminder_list).

From the tool's definition Tool description states 'Rename an existing reminder list' — this modifies metadata of an existing list. The action is reversible (the list can be renamed again to any other name).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Reminders MCP Server, so you can run agents against it safely.

FAQ

Questions about rename_reminder_list

What does the rename_reminder_list tool do? +

Rename an existing reminder list. It is categorised as a Write tool in the Reminders MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_reminder_list? +

Register the Reminders MCP Server 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 Reminders MCP Server. 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 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.