Migrate existing subtasks to the unified task model. This tool converts all subtasks to tasks with parentId for unlimited nesting depth. Run this once after upgrading to ensure data compatibility.
AI agents use migrate_subtasks 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 modifies existing data (subtasks) by converting them to a new model format. While not permanently destructive (data is transformed, not deleted), it is a Write operation that alters multiple records' structure and relationships.
From the tool's definition Tool description states 'converts all subtasks to tasks' and 'migrate existing subtasks', indicating modification of data structure across potentially all subtask records. The migration operation transforms data format irreversibly for compatibility.
Documented attack patterns abuse exactly the kind of access migrate_subtasks 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 migrate_subtasks:
{
"version": "1",
"default": "deny",
"tools": {
"migrate_subtasks": {
"limits": [
{
"counter": "migrate_subtasks_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}migrate_subtasks 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.
Migrate existing subtasks to the unified task model. This tool converts all subtasks to tasks with parentId for unlimited nesting depth. Run this once after upgrading to ensure data compatibility. 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 migrate_subtasks: 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.
migrate_subtasks 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 migrate_subtasks 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 migrate_subtasks. 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.
migrate_subtasks 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.