重命名一个文件或目录。
AI agents use mcp_file_rename to create or update resources in ShowDoc MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ShowDoc MCP Server environment.
File renaming is a write operation that reversibly modifies data (the file name/path structure) but does not delete or execute code. It has medium severity because careless renaming could break file references or project structure, but the effect is recoverable through renaming again. Confidence is 0.85 due to the non-English description, though the intent is clear from the tool name and 'mcp_' prefix pattern.
From the tool's definition Tool name 'mcp_file_rename' and description '重命名一个文件或目录' (rename a file or directory) indicate the tool modifies filesystem metadata by changing file/directory names.
Attacks that exploit this kind of access
重命名一个文件或目录。. It is categorised as a Write tool in the ShowDoc MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ShowDoc MCP Server MCP server in PolicyLayer and add a rule for mcp_file_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 ShowDoc MCP Server. Nothing to install.
mcp_file_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 mcp_file_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 mcp_file_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.
mcp_file_rename is provided by the ShowDoc MCP Server MCP server (yfcyfc123234/showdoc_mcp). 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 →