lsp_rename_symbol · LocalAnt MCP: Risk & Policy

WHAT IT DOES

What lsp_rename_symbol does on LocalAnt

AI agents use lsp_rename_symbol to create or update resources in LocalAnt — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LocalAnt environment.

WHY IT NEEDS A POLICY

Why lsp_rename_symbol needs a policy

This tool performs a language-aware refactoring operation that updates symbol references across a project. While the changes are reversible (can be undone via version control), it materially modifies source code in multiple locations, making it Write rather than Read or Execute. The 'Risk 2' annotation suggests moderate concern. It is not Destructive (changes are reversible) or Financial.

From the tool's definition Tool description states 'Rename the symbol at a 1-indexed line/character across the project' — this modifies code across multiple files in a codebase, which is a reversible but non-trivial code change operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lsp_rename_symbol Rate-limited

lsp_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lsp_rename_symbol": {
      "limits": [
        {
          "counter": "lsp_rename_symbol_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LocalAnt, so you can run agents against it safely.

FAQ

Questions about lsp_rename_symbol

What does the lsp_rename_symbol tool do? +

Rename the symbol at a 1-indexed line/character across the project (TypeScript/JavaScript). Risk 2. It is categorised as a Write tool in the LocalAnt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on lsp_rename_symbol? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for lsp_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 LocalAnt. Nothing to install.

What risk level is lsp_rename_symbol? +

lsp_rename_symbol is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit lsp_rename_symbol? +

Yes. Add a rate_limit block to the lsp_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.

How do I block lsp_rename_symbol completely? +

Set action: deny in the PolicyLayer policy for lsp_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.

What MCP server provides lsp_rename_symbol? +

lsp_rename_symbol is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.