repair_import_paths · TypeScript Tools MCP: Risk & Policy

WHAT IT DOES

What repair_import_paths does on TypeScript Tools MCP

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

This tool modifies source code by updating import paths in files, which is a reversible write operation. While it could potentially cause issues if it updates imports to incorrect locations, the operation itself can be undone (files can be reverted or imports corrected again). It does not execute arbitrary code, delete files, or perform financial operations.

From the tool's definition Tool description states it will "repair broken import paths in TypeScript files by finding the correct file location and updating import statements." The phrase "updating import statements" indicates modification of existing code files.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

repair_import_paths Rate-limited

repair_import_paths 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": {
    "repair_import_paths": {
      "limits": [
        {
          "counter": "repair_import_paths_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 repair_import_paths

What does the repair_import_paths tool do? +

Automatically detect and repair broken import paths in TypeScript files by finding the correct file location and updating import statements. 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 repair_import_paths? +

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

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

Can I rate-limit repair_import_paths? +

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

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

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