Re-point an existing file_node at a new path (rename / move).
AI agents use files_link_rename to create or update resources in M3 Memory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your M3 Memory environment.
Renaming or moving files changes file system state but does not irreversibly destroy data (Destructive category). The operation is reversible (can rename back or move to original location), characteristic of Write operations. Severity is medium because incorrect renames could cause application failures or data access issues, but damage is recoverable.
From the tool's definition Tool description states 'Re-point an existing file_node at a new path (rename / move)' — this modifies file metadata/location, a reversible write operation.
Documented attack patterns abuse exactly the kind of access files_link_rename gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and M3 Memory, and nothing reaches the server without passing your rules. This is the rule we recommend for files_link_rename:
{
"version": "1",
"default": "deny",
"tools": {
"files_link_rename": {
"limits": [
{
"counter": "files_link_rename_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}files_link_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.
Free to start. No card required.
Re-point an existing file_node at a new path (rename / move). It is categorised as a Write tool in the M3 Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the M3 Memory MCP server in PolicyLayer and add a rule for files_link_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 M3 Memory. Nothing to install.
files_link_rename 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 files_link_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.
Set action: deny in the PolicyLayer policy for files_link_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.
files_link_rename is provided by the M3 Memory MCP server (skynetcmd/m3-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from M3 Memory, 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.
43 M3 Memory tools catalogued and risk-classified — across an index of 43,000+ MCP servers.