This record as markdown: /tools/eaveluo-1panel-mcp/rename-file.md
What rename_file does on 1Panel MCP Server
AI agents use rename_file to create or update resources in 1Panel MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 1Panel MCP Server environment.
Why rename_file is rated Medium
Renaming files/directories is a reversible write operation that modifies file system metadata. While it alters state, it does not delete data, execute code, or cause financial impact. The medium severity reflects that misuse could disrupt system organization or application functionality, but the operation can be undone by renaming again.
From the tool's definition Tool name 'rename_file' and description 'Rename file/directory' indicate modification of file metadata without deletion or creation of new data.
Attacks that exploit this kind of access
The rule that runs rename_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1Panel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rename_file, this is the rule to start with:
rename_file 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 1Panel MCP Server, apply this rule, and every rename_file call is checked against it from then on.
Questions about rename_file
Rename file/directory. It is categorised as a Write tool in the 1Panel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 1Panel MCP Server MCP server in PolicyLayer and add a rule for rename_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 1Panel MCP Server. Nothing to install.
rename_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 rename_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 rename_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.
rename_file is provided by the 1Panel MCP Server MCP server (eaveluo/1panel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1Panel MCP Server, and thousands of servers like it.
This server
Across the catalogue