rename · Mnemosyne MCP: Risk & Policy

WHAT IT DOES

What rename does on Mnemosyne MCP

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

WHY IT NEEDS A POLICY

Why rename needs a policy

Rename modifies metadata (names/identifiers) of existing entities in the knowledge graph, making it a Write operation rather than Read (it changes state) or Destructive (it is reversible). Severity is medium because renaming could confuse users or break references if applied incorrectly, but the operation is undoable.

From the tool's definition Tool named 'rename' on a Mnemosyne knowledge graph management server; sibling tools include 'create_graph', 'create_folder', 'delete', and 'document_digest', indicating data manipulation operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename Rate-limited

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

FAQ

Questions about rename

What does the rename tool do? +

rename. It is categorised as a Write tool in the Mnemosyne 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 rename? +

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

What risk level is rename? +

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

Can I rate-limit rename? +

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

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

rename is provided by the Mnemosyne MCP server (sophia-labs/mnemosyne-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.