Rename a file or folder using LSP rename capabilities
AI agents use rename_file to create or update resources in LSP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LSP MCP Server environment.
This tool creates or modifies metadata (filenames/folder names) which is reversible, placing it in the Write category rather than Destructive. However, it scores high severity because renaming files can break imports, references, and build systems if an AI agent renames files incorrectly without understanding the codebase impact, potentially causing significant disruption to a project structure.
From the tool's definition The tool performs 'rename_file' or 'folder' which is described as 'Rename a file or folder using LSP rename capabilities'. Renaming files/folders is a reversible modification that changes data organization and metadata.
Documented attack patterns abuse exactly the kind of access rename_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LSP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for rename_file:
{
"version": "1",
"default": "deny",
"tools": {
"rename_file": {
"limits": [
{
"counter": "rename_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Rename a file or folder using LSP rename capabilities. It is categorised as a Write tool in the LSP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LSP 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 LSP 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 LSP MCP Server MCP server (sminnee/lsp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LSP MCP Server, 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.
5 LSP MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.