AI agents use move_file to create or update resources in Nutstore — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nutstore environment.
File movement and renaming are Write operations: they modify metadata and structure within the storage system but remain reversible, distinguishing them from Destructive actions (delete, purge). The severity is medium because misuse could disrupt file organization and user workflows, but the impact is recoverable via moving files back to original locations.
From the tool's definition move_file: '移动或重命名坚果云中的文件/目录' (move or rename files/directories in Nutstore cloud storage). The operation modifies file/directory structure but is reversible—files can be moved back or renamed again.
Attacks that exploit this kind of access
移动或重命名坚果云中的文件/目录. It is categorised as a Write tool in the Nutstore MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nutstore MCP server in PolicyLayer and add a rule for move_file: 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 Nutstore. Nothing to install.
move_file 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_file 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_file. 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_file is provided by the Nutstore MCP server (silverze/nutstore-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
move_file is one line of Nutstore's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →