memory_rename_project · Claude Memory MCP: Risk & Policy

WHAT IT DOES

What memory_rename_project does on Claude Memory MCP

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

WHY IT NEEDS A POLICY

Why memory_rename_project needs a policy

The tool modifies project metadata (display name and description) in a way that can be undone by renaming again or updating the description further. This is a classic Write operation—data is being created or modified reversibly. The operation has no financial implications, does not execute code or commands, does not permanently destroy data, and does not trigger external operations with uncontrolled side effects.

From the tool's definition Tool description states it can "Rename a project (its display name) and optionally update its description." These are reversible metadata modifications that create or change data without deletion or irreversible side effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_rename_project Rate-limited

memory_rename_project 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": {
    "memory_rename_project": {
      "limits": [
        {
          "counter": "memory_rename_project_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 Claude Memory MCP, so you can run agents against it safely.

FAQ

Questions about memory_rename_project

What does the memory_rename_project tool do? +

Rename a project (its display name) and optionally update its description. It is categorised as a Write tool in the Claude Memory MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory_rename_project? +

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

What risk level is memory_rename_project? +

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

Can I rate-limit memory_rename_project? +

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

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

memory_rename_project is provided by the Claude Memory MCP server (navid-kianfar/claude-memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.