[ts-morph] Type-aware rename of a TypeScript/JavaScript symbol (function, variable, class, type, interface, enum, etc.) across the entire project. When to use - Renaming any symbol that may be imported, re-exported, or referenced in other files. - Prefer this over manual Edit + grep / sed. Identi...
AI agents use rename_symbol_by_tsmorph to create or update resources in MCP ts-morph Refactoring Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP ts-morph Refactoring Tools environment.
This tool modifies code by renaming symbols across a project, which constitutes a Write operation—it creates or modifies data reversibly. While the blast radius is moderate (an incorrect rename could break many files), the operation is not destructive (not irreversible), not financial, and not arbitrary code execution.
From the tool's definition Tool description states it performs 'Type-aware rename of a TypeScript/JavaScript symbol (function, variable, class, type, interface, enum, etc.) across the entire project.' Renaming is a modification operation that creates new identifiers and updates…
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access rename_symbol_by_tsmorph gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP ts-morph Refactoring Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for rename_symbol_by_tsmorph:
{
"version": "1",
"default": "deny",
"tools": {
"rename_symbol_by_tsmorph": {
"limits": [
{
"counter": "rename_symbol_by_tsmorph_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}rename_symbol_by_tsmorph 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.
[ts-morph] Type-aware rename of a TypeScript/JavaScript symbol (function, variable, class, type, interface, enum, etc.) across the entire project. When to use - Renaming any symbol that may be imported, re-exported, or referenced in other files. - Prefer this over manual Edit + grep / sed. Identifier-based search misses re-exports, JSX attribute usage, and matches unrelated same-name tokens. This tool resolves references via the type checker, so it is both safer and faster. - Even for a. It is categorised as a Write tool in the MCP ts-morph Refactoring Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP ts-morph Refactoring Tools MCP server in PolicyLayer and add a rule for rename_symbol_by_tsmorph: 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 MCP ts-morph Refactoring Tools. Nothing to install.
rename_symbol_by_tsmorph 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_by_tsmorph 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_by_tsmorph. 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_by_tsmorph is provided by the MCP ts-morph Refactoring Tools MCP server (sirosuzume/mcp-ts-morph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP ts-morph Refactoring Tools, 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.
8 MCP ts-morph Refactoring Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.