Remove a dependency between two tasks. Args: task_id: ID of the task with the dependency depends_on_id: ID of the dependency to remove Returns: Confirmation with updated task info
AI agents use remove_dependency to create or update resources in Taskdog — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Taskdog environment.
Removing a dependency modifies the task relationship data but does not delete the tasks themselves. This is a reversible write operation (the dependency could be re-added), affecting task scheduling and execution order. Misuse could disrupt task ordering logic but is not irreversible destruction of data.
From the tool's definition Remove a dependency between two tasks
Documented attack patterns abuse exactly the kind of access remove_dependency gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Taskdog, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_dependency:
{
"version": "1",
"default": "deny",
"tools": {
"remove_dependency": {
"limits": [
{
"counter": "remove_dependency_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}remove_dependency 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.
Remove a dependency between two tasks. Args: task_id: ID of the task with the dependency depends_on_id: ID of the dependency to remove Returns: Confirmation with updated task info. It is categorised as a Write tool in the Taskdog MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Taskdog MCP server in PolicyLayer and add a rule for remove_dependency: 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 Taskdog. Nothing to install.
remove_dependency 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 remove_dependency 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 remove_dependency. 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.
remove_dependency is provided by the Taskdog MCP server (kohei-wada/taskdog). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Taskdog, 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.
26 Taskdog tools catalogued and risk-classified — across an index of 43,000+ MCP servers.