Move a task to a different position or parent within the same list, or to a different list
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.
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.
Documented attack patterns abuse exactly the kind of access move_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VaultAssist, and nothing reaches the server without passing your rules. This is the rule we recommend for move_task:
{
"version": "1",
"default": "deny",
"tools": {
"move_task": {
"limits": [
{
"counter": "move_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
Start from VaultAssist, 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.
79 VaultAssist tools catalogued and risk-classified — across an index of 43,000+ MCP servers.