move_folder
AI agents use move_folder 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.
Moving a folder within a knowledge graph structure is a Write operation—it modifies the graph's organization but is reversible (can be moved again). It does not delete data (not Destructive), execute arbitrary code (not Execute), or involve financial transactions (not Financial).
From the tool's definition Tool name 'move_folder' indicates a folder/node reorganization operation within a knowledge graph. The broader server context confirms this is a graph management operation (alongside create_folder, create_graph, delete).
Attacks that exploit this kind of access
move_folder. 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.
Register the Mnemosyne MCP server in PolicyLayer and add a rule for move_folder: 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.
move_folder is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the move_folder 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.
Set action: deny in the PolicyLayer policy for move_folder. 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.
move_folder 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →