[ts-morph] Move one top-level symbol (function, variable, class, interface, type, enum) from one file to another, carrying its internal-only dependencies and rewriting all imports/exports across the project. When to use - Splitting a large file: move related symbols to a new file one by one. - Re...
AI agents use move_symbol_to_file_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 creates and modifies code files by relocating symbols and updating import/export statements across the codebase. While the changes are reversible (via version control or undo), the blast radius is significant: incorrect symbol moves could break imports, create circular dependencies, or corrupt the project structure across multiple files simultaneously.
From the tool's definition Tool moves symbols between files and rewrites imports/exports across the project, which modifies file contents and project structure.
Documented attack patterns abuse exactly the kind of access move_symbol_to_file_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 move_symbol_to_file_by_tsmorph:
{
"version": "1",
"default": "deny",
"tools": {
"move_symbol_to_file_by_tsmorph": {
"limits": [
{
"counter": "move_symbol_to_file_by_tsmorph_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_symbol_to_file_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] Move one top-level symbol (function, variable, class, interface, type, enum) from one file to another, carrying its internal-only dependencies and rewriting all imports/exports across the project. When to use - Splitting a large file: move related symbols to a new file one by one. - Relocating a helper from a generic \. 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 move_symbol_to_file_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.
move_symbol_to_file_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 move_symbol_to_file_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 move_symbol_to_file_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.
move_symbol_to_file_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.