move_path
A write tool on the Mapi Agent Memory MCP server.
This record as markdown: /tools/mapi-agent-memory/move-path.md
What move_path does on Mapi Agent Memory
AI agents use move_path to create or update resources in Mapi Agent Memory, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mapi Agent Memory environment.
Why move_path is rated Medium
move_path most likely creates or modifies the organization of data (moving entries, updating references) rather than irreversibly deleting it, placing it in the Write category. It is not Destructive because moving/reorganizing is typically reversible. Without an explicit description, confidence is moderate (0.75).
From the tool's definition Tool name 'move_path' suggests file or path manipulation operations. Given the server context of 'Auditable memory and governance for AI agents,' this likely moves or reorganizes memory entries or file pointers.
Attacks that exploit this kind of access
The rule that runs move_path safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mapi Agent Memory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_path, this is the rule to start with:
move_path 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mapi Agent Memory, apply this rule, and every move_path call is checked against it from then on.
Questions about move_path
move_path is a write tool on the Mapi Agent Memory MCP server. It is categorised as a Write tool in the Mapi Agent Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for move_path: 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 Mapi Agent Memory. Nothing to install.
move_path 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_path 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_path. 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_path is provided by the Mapi Agent Memory MCP server (cabo0m/mapi-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mapi Agent Memory, and thousands of servers like it.
This server
Across the catalogue