AI agents use rename_file to create or update resources in Baidu Pan — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Baidu Pan environment.
Renaming files is a write operation that modifies metadata reversibly. It does not execute code, delete data irreversibly, or transfer funds. While it can cause confusion if misused (e.g., renaming critical files), the blast radius is limited to the affected file's metadata and remains recoverable. Medium severity reflects potential for user disruption without permanent data loss.
From the tool's definition Tool name 'rename_file' and description indicating file/folder renaming on Baidu Pan (百度网盘中的文件或文件夹). Renaming is a metadata modification operation that creates a new state but is reversible—the original name can be renamed back.
Attacks that exploit this kind of access
重命名百度网盘中的文件或文件夹. It is categorised as a Write tool in the Baidu Pan MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Baidu Pan 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 Baidu Pan. 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 Baidu Pan MCP server (xileforcly/baidu-pan-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →