Move a task to a different parent in the hierarchy. Set newParentId to move under another task, or leave empty to move to top level. Supports unlimited nesting depth.
AI agents use move_task to create or update resources in Agentic Tools MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agentic Tools MCP Server environment.
This tool changes task metadata (parent reference) but does not delete data or create irreversible side effects. The modification is reversible — a task can be moved again to restore its prior position. This places it in Write (data modification) rather than Destructive.
From the tool's definition Tool performs 'Move a task to a different parent in the hierarchy' — modifies the structural relationship and hierarchical position of a task, which is a reversible data modification operation.
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 Agentic Tools MCP Server, 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 parent in the hierarchy. Set newParentId to move under another task, or leave empty to move to top level. Supports unlimited nesting depth. It is categorised as a Write tool in the Agentic Tools MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agentic Tools MCP Server 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 Agentic Tools MCP Server. 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 Agentic Tools MCP Server MCP server (pimzino/agentic-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Agentic Tools MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 Agentic Tools MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.