move_task
Move a task to a different position or parent within the same list, or to a different list
This record as markdown: /tools/3xcaffeine-mcp-server/move-task.md
What move_task does on VaultAssist
AI agents use move_task to create or update resources in VaultAssist, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VaultAssist environment.
Why move_task is rated Medium
Moving a task changes its organizational structure (position, parent, or list assignment) but does not delete, execute external commands, or create permanent loss of data. The operation is reversible—a task can be moved back to its original location. While it modifies data, it does not rise to Destructive (irreversible deletion), Execute (code/external triggers), or Financial severity.
From the tool's definition Tool name 'move_task' and description indicates it modifies task state by changing position or parent/list assignment. This is a reversible modification operation typical of Write category tools.
Attacks that exploit this kind of access
The rule that runs move_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and VaultAssist, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_task, this is the rule to start with:
move_task 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.
The button opens the PolicyLayer dashboard: create your workspace, connect VaultAssist, apply this rule, and every move_task call is checked against it from then on.
Questions about move_task
Move a task to a different position or parent within the same list, or to a different list. It is categorised as a Write tool in the VaultAssist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the VaultAssist MCP server in PolicyLayer and add a rule for move_task: 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 VaultAssist. Nothing to install.
move_task 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_task 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_task. 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_task is provided by the VaultAssist MCP server (3xcaffeine/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on VaultAssist, and thousands of servers like it.
This server
Across the catalogue