move_typescript_file · TypeScript Tools MCP: Risk & Policy

WHAT IT DOES

What move_typescript_file does on TypeScript Tools MCP

AI agents use move_typescript_file 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 move_typescript_file needs a policy

Moving a file relocates it on the filesystem and rewrites import paths across the codebase. This is reversible in principle (files can be moved back, imports restored), so it falls under Write rather than Destructive. However, the blast radius is high because it modifies multiple files across a project — an incorrect move could break imports widely and require significant manual repair.

From the tool's definition 'Move a TypeScript file and update all import paths automatically'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_typescript_file Rate-limited

move_typescript_file 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": {
    "move_typescript_file": {
      "limits": [
        {
          "counter": "move_typescript_file_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 move_typescript_file

What does the move_typescript_file tool do? +

Move a TypeScript file and update all import paths automatically. 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 move_typescript_file? +

Register the TypeScript Tools MCP server in PolicyLayer and add a rule for move_typescript_file: 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 move_typescript_file? +

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

Can I rate-limit move_typescript_file? +

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

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

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