createTaskDependency
Create an FS/SS/FF scheduling edge with lag/lead between two items in the same plan (rendered as a Gantt arrow). FS = Finish-to-Start, SS = Start-to-Start, FF = Finish-to-Finish. lagDays: positive = lag, negative = lead/overlap. Rejects self-loops, duplicate (pred+succ+type) edges, cross-plan edg...
This record as markdown: /tools/io-stablebaseline-sb/createtaskdependency.md
What createTaskDependency does on Stable Baseline
AI agents use createTaskDependency to create or update resources in Stable Baseline, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stable Baseline environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
lagDays | integer | — | Lag (positive) or lead (negative) in days. Default 0. |
successorId | string | Yes | ID of the downstream item (the dependent). |
predecessorId | string | Yes | ID of the upstream item (the driver). |
dependencyType | string | Yes | FS = Finish-to-Start, SS = Start-to-Start, FF = Finish-to-Finish. |
Parameters from the server's own tool schema.
Why createTaskDependency is rated Medium
This tool creates new data structures (task dependencies/Gantt arrows) within a plan, which is reversible and aligns with Write category. It does not delete, execute arbitrary code, or move money. The medium severity reflects that incorrect dependencies could disrupt project schedules and require correction, but the impact is scoped to a single plan and the operation is reversible (dependencies can be removed).
From the tool's definition Tool description explicitly states it creates scheduling edges (dependencies) between tasks: 'Create an FS/SS/FF scheduling edge... between two items in the same plan'.
Attacks that exploit this kind of access
The rule that runs createTaskDependency 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 createTaskDependency, this is the rule to start with:
createTaskDependency 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every createTaskDependency call is checked against it from then on.
Questions about createTaskDependency
Create an FS/SS/FF scheduling edge with lag/lead between two items in the same plan (rendered as a Gantt arrow). FS = Finish-to-Start, SS = Start-to-Start, FF = Finish-to-Finish. lagDays: positive = lag, negative = lead/overlap. Rejects self-loops, duplicate (pred+succ+type) edges, cross-plan edges, and cycles. It is categorised as a Write tool in the Stable Baseline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
createTaskDependency accepts 4 parameters: lagDays, successorId, predecessorId, dependencyType. Required: successorId, predecessorId, dependencyType. 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 createTaskDependency: 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.
createTaskDependency 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 createTaskDependency 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 createTaskDependency. 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.
createTaskDependency 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.
This server
Across the catalogue