Move a memory to a different to_workspace.
AI agents use move_memory to create or update resources in Memlord — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memlord environment.
This tool modifies the state of data (changing a memory's workspace location) in a way that is reversible and does not irreversibly delete, destroy, execute code, or transfer financial value. It falls clearly into the Write category. Severity is medium because misuse could disorganize personal or team memory structures, but the effect is not as damaging as deletion (Destructive) or code execution (Execute).
From the tool's definition 'Move a memory to a different to_workspace' indicates a reversible data modification operation. The memory is relocated but not deleted, and the action can be undone by moving it back.
Documented attack patterns abuse exactly the kind of access move_memory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memlord, and nothing reaches the server without passing your rules. This is the rule we recommend for move_memory:
{
"version": "1",
"default": "deny",
"tools": {
"move_memory": {
"limits": [
{
"counter": "move_memory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_memory 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.
Free to start. No card required.
Move a memory to a different to_workspace. It is categorised as a Write tool in the Memlord MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memlord MCP server in PolicyLayer and add a rule for move_memory: 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 Memlord. Nothing to install.
move_memory 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_memory 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_memory. 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_memory is provided by the Memlord MCP server (myrikld/memlord). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memlord, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Memlord tools catalogued and risk-classified — across an index of 43,000+ MCP servers.