apply_move

Move a symbol to a different file or rename/move a file, updating all import paths across the codebase. Dry-run by default (safe preview). Modifies source files. Use plan_refactoring with type=

SERVERTrace SOURCEnikolai-vysotskyi/trace-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/apply-move.md

WHAT IT DOES

What apply_move does on Trace

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

RISK

Why apply_move is rated Medium

apply_move performs reversible modifications to source code (moving symbols/files and updating imports). It does not delete data irreversibly (thus not Destructive), nor does it execute arbitrary code or external commands (thus not Execute). The tool defaults to dry-run mode for safety, which further supports Write rather than higher-severity categories.

From the tool's definition Tool description states: 'Move a symbol to a different file or rename/move a file, updating all import paths across the codebase' and 'Modifies source files.' These are clear write operations that create/modify code files.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs apply_move safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For apply_move, this is the rule to start with:

apply_move Rate-limited

apply_move 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": {
    "apply_move": {
      "limits": [
        {
          "counter": "apply_move_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every apply_move call is checked against it from then on.

FAQ

Questions about apply_move

What does the apply_move tool do? +

Move a symbol to a different file or rename/move a file, updating all import paths across the codebase. Dry-run by default (safe preview). Modifies source files. Use plan_refactoring with type=. It is categorised as a Write tool in the Trace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on apply_move? +

Register the Trace MCP server in PolicyLayer and add a rule for apply_move: 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 Trace. Nothing to install.

What risk level is apply_move? +

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

Can I rate-limit apply_move? +

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

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

apply_move is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Trace, and thousands of servers like it.

This server

All 191 Trace tools →

Across the catalogue

binary_patch_apply on 010 Editor →move-task on Kanban MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →