rename_list · RTM MCP Server MCP: Risk & Policy

WHAT IT DOES

What rename_list does on RTM MCP Server

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

WHY IT NEEDS A POLICY

Why rename_list needs a policy

Renaming a list is a write operation that modifies metadata reversibly. The blast radius is medium because renaming a list could cause confusion if done incorrectly on shared task lists, but the action is easily undone by renaming again. This does not rise to Execute (no code/commands triggered), Destructive (not irreversible), or Financial (no money involved). It fits Write as it creates or modifies data reversibly.

From the tool's definition Tool name 'rename_list' and description 'Rename a list' indicate modification of existing data. The Remember The Milk API context shows this is a reversible operation (renaming), not deletion or financial action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_list Rate-limited

rename_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_list": {
      "limits": [
        {
          "counter": "rename_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 RTM MCP Server, so you can run agents against it safely.

FAQ

Questions about rename_list

What does the rename_list tool do? +

Rename a list. It is categorised as a Write tool in the RTM 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_list? +

Register the RTM MCP Server MCP server in PolicyLayer and add a rule for rename_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 RTM MCP Server. Nothing to install.

What risk level is rename_list? +

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

Can I rate-limit rename_list? +

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

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

rename_list is provided by the RTM MCP Server MCP server (ljadach/rtm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.