rename_typescript_symbol · TypeScript Tools MCP

WHAT IT DOES

What rename_typescript_symbol does on TypeScript Tools MCP

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

WHY IT NEEDS A POLICY

Why rename_typescript_symbol needs a policy

This tool modifies code by changing identifier names and propagating those changes across files. While reversible (can be undone via version control), it alters source code structure. It does not delete data (which would be Destructive), execute arbitrary commands (Execute), or handle finances (Financial).

From the tool's definition Tool name 'rename_typescript_symbol' and description 'Rename a variable, function, type, interface, or class and update all references' indicates creation/modification of code symbols and cascading updates throughout a codebase.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_typescript_symbol Rate-limited

rename_typescript_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": {
    "rename_typescript_symbol": {
      "limits": [
        {
          "counter": "rename_typescript_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 TypeScript Tools MCP, so you can run agents against it safely.

FAQ

Questions about rename_typescript_symbol

What does the rename_typescript_symbol tool do? +

Rename a variable, function, type, interface, or class and update all references. It is categorised as a Write tool in the TypeScript Tools MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_typescript_symbol? +

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

What risk level is rename_typescript_symbol? +

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

Can I rate-limit rename_typescript_symbol? +

Yes. Add a rate_limit block to the rename_typescript_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 rename_typescript_symbol completely? +

Set action: deny in the PolicyLayer policy for rename_typescript_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 rename_typescript_symbol? +

rename_typescript_symbol is provided by the TypeScript Tools MCP server (trkbt10/mcp-typescript-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.