Rename a symbol (variable, function, class, etc.) across all files
AI agents use rename_symbol 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.
Renaming symbols is a write operation that creates modified versions of code artifacts. While reversible through version control, it changes code state across multiple files simultaneously. The confidence is high (0.9) because the description clearly indicates modification of code symbols across a codebase.
From the tool's definition The tool performs renaming operations that 'across all files' modifies code symbols. The description indicates it changes variable, function, and class names, which are write operations that alter source code.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access rename_symbol 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_symbol:
{
"version": "1",
"default": "deny",
"tools": {
"rename_symbol": {
"limits": [
{
"counter": "rename_symbol_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}rename_symbol 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 symbol (variable, function, class, etc.) across all files. 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_symbol: 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_symbol 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_symbol 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_symbol. 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_symbol 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.