deleteTaskDependency
Remove a task-dependency edge. Neither item's dates are changed.
This record as markdown: /tools/io-stablebaseline-sb/deletetaskdependency.md
What deleteTaskDependency does on Stable Baseline
AI agents call deleteTaskDependency to permanently remove resources in Stable Baseline, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
dependencyId | string | Yes |
Parameters from the server's own tool schema.
Why deleteTaskDependency is rated Critical
Deleting task dependencies cannot be undone and will break project planning relationships. While it doesn't delete the tasks themselves, it irreversibly removes structured data (the edge) from the system's task dependency graph. This affects downstream planning and could cascade impacts if dependent plans rely on that relationship.
From the tool's definition Tool name includes 'delete' and description states 'Remove a task-dependency edge', indicating irreversible removal of a relationship object in the knowledge graph.
Attacks that exploit this kind of access
The rule that runs deleteTaskDependency safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deleteTaskDependency, this is the rule to start with:
deleteTaskDependency is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every deleteTaskDependency call is checked against it from then on.
Questions about deleteTaskDependency
Remove a task-dependency edge. Neither item's dates are changed. It is categorised as a Destructive tool in the Stable Baseline MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
deleteTaskDependency accepts 1 parameter: dependencyId. Required: dependencyId. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for deleteTaskDependency: 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 Stable Baseline. Nothing to install.
deleteTaskDependency is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteTaskDependency 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 deleteTaskDependency. 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.
deleteTaskDependency is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
Across the catalogue