Move a ${harnessName} configuration item from one scope to another. Run scan_inventory first to see available items and scope IDs.
AI agents use move_item to create or update resources in Claude Code Organizer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Code Organizer environment.
This tool modifies configuration state by relocating items between scopes in Claude Code's hierarchy. While the change is reversible (the item is not deleted, merely repositioned), it alters system state and could disrupt code organization if misused. It does not execute external commands, delete data irreversibly, or commit financial transactions, so Write is the appropriate category.
From the tool's definition Tool description explicitly states it 'Move[s] a configuration item from one scope to another,' which modifies the location/state of data within the system. The word 'move' indicates a reversible relocation rather than deletion.
Documented attack patterns abuse exactly the kind of access move_item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Code Organizer, and nothing reaches the server without passing your rules. This is the rule we recommend for move_item:
{
"version": "1",
"default": "deny",
"tools": {
"move_item": {
"limits": [
{
"counter": "move_item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_item 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 ${harnessName} configuration item from one scope to another. Run scan_inventory first to see available items and scope IDs. It is categorised as a Write tool in the Claude Code Organizer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Code Organizer MCP server in PolicyLayer and add a rule for move_item: 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 Claude Code Organizer. Nothing to install.
move_item 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_item 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_item. 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_item is provided by the Claude Code Organizer MCP server (mcpware/cross-code-organizer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Code Organizer, 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.
5 Claude Code Organizer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.