rename_agent · Todos MCP: Risk & Policy

WHAT IT DOES

What rename_agent does on Todos

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

WHY IT NEEDS A POLICY

Why rename_agent needs a policy

Renaming is a modification operation that changes data (the agent's name) but is fully reversible—the original name can be restored. This falls under Write rather than Execute or Destructive.

From the tool's definition The tool is named 'rename_agent' and described as 'Rename an agent. Resolve by id or current name.' This modifies metadata about an agent (its name) reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_agent Rate-limited

rename_agent 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_agent": {
      "limits": [
        {
          "counter": "rename_agent_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 Todos, so you can run agents against it safely.

FAQ

Questions about rename_agent

What does the rename_agent tool do? +

Rename an agent. Resolve by id or current name. It is categorised as a Write tool in the Todos 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_agent? +

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

What risk level is rename_agent? +

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

Can I rate-limit rename_agent? +

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

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

rename_agent is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.