New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

move_task

Move a task to a different position or parent within the same list, or to a different list

SERVERVaultAssist SOURCE3xcaffeine/mcp-server
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/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.

Questions about move_task

What does the move_task tool do? +

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.

How do I enforce a policy on move_task? +

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.

What risk level is move_task? +

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

Can I rate-limit move_task? +

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.

How do I block move_task completely? +

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.

What MCP server provides move_task? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of VaultAssist's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.