move_documents · Mnemosyne MCP: Risk & Policy

WHAT IT DOES

What move_documents does on Mnemosyne MCP

AI agents use move_documents 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 move_documents needs a policy

The tool name 'move_documents' most directly maps to Write category—it reorganizes existing data reversibly (documents can be moved again). While the empty description limits certainty, context from sibling tools (delete, create_folder, create_graph) confirms this is a data-manipulation platform. Move operations are reversible and non-destructive, distinguishing them from 'delete'.

From the tool's definition Tool name 'move_documents' indicates it modifies document location/organization; sibling tools include 'delete' (destructive) and 'create_folder' (write), suggesting this server manages document/knowledge graph state. Description is empty, reducing confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_documents Rate-limited

move_documents 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": {
    "move_documents": {
      "limits": [
        {
          "counter": "move_documents_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 move_documents

What does the move_documents tool do? +

move_documents. 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 move_documents? +

Register the Mnemosyne MCP server in PolicyLayer and add a rule for move_documents: 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 move_documents? +

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

Can I rate-limit move_documents? +

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

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

move_documents 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.