Moves tasks between workflow states. Automatically updates status based on transition unless disabled. Archive moves require YYYY-MM date.
AI agents use task_move to create or update resources in Scopecraft Command — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Scopecraft Command environment.
This tool modifies the state of tasks (changing workflow states, updating status) within a task management system. These changes are reversible—tasks can be moved to other states or restored—distinguishing it from destructive operations. The automatic status updates constitute data modification.
From the tool's definition Moves tasks between workflow states and automatically updates status based on transition, indicating reversible modification of task data and state metadata.
Documented attack patterns abuse exactly the kind of access task_move gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Scopecraft Command, and nothing reaches the server without passing your rules. This is the rule we recommend for task_move:
{
"version": "1",
"default": "deny",
"tools": {
"task_move": {
"limits": [
{
"counter": "task_move_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}task_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.
Moves tasks between workflow states. Automatically updates status based on transition unless disabled. Archive moves require YYYY-MM date. It is categorised as a Write tool in the Scopecraft Command MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Scopecraft Command MCP server in PolicyLayer and add a rule for task_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 Scopecraft Command. Nothing to install.
task_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 task_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 task_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.
task_move is provided by the Scopecraft Command MCP server (scopecraft/command). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Scopecraft Command tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 Scopecraft Command tools catalogued and risk-classified — across an index of 42,500+ MCP servers.