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=
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.
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.
Documented attack patterns abuse exactly the kind of access apply_move gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trace, and nothing reaches the server without passing your rules. This is the rule we recommend for apply_move:
{
"version": "1",
"default": "deny",
"tools": {
"apply_move": {
"limits": [
{
"counter": "apply_move_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.
apply_move 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 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.
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.
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.
Deterministic rules across all 178 Trace tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
178 Trace tools catalogued and risk-classified — across an index of 42,500+ MCP servers.