applyTaskDependencyCascade
Auto-schedule every item in a plan so all FS/SS/FF task-dependencies are respected (topological pass, durations preserved). Returns the before/after diff and logs a comment on every item that moves. Use forwardOnly: true to only shift items currently in violation (never pull already-valid items e...
This record as markdown: /tools/io-stablebaseline-sb/applytaskdependencycascade.md
What applyTaskDependencyCascade does on Stable Baseline
AI agents use applyTaskDependencyCascade 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 |
|---|---|---|---|
planId | string | Yes | Plan to reschedule. |
forwardOnly | boolean | — | When true, only shift items currently in violation — never pull already-valid items to an earlier slot. Default false for backwards compat with the manual Auto- |
pinnedItemIds | array | — | Item IDs to keep at their current dates (typical: the item you just updated). |
Parameters from the server's own tool schema.
Why applyTaskDependencyCascade is rated Medium
The tool modifies plan data by rescheduling tasks based on dependency constraints. While it changes dates across potentially many items ('cascade' effect affecting all dependent tasks), these modifications are reversible (can be undone via subsequent writes). It does not delete data or execute arbitrary code, making it Write rather than Destructive or Execute.
From the tool's definition Tool auto-schedules and modifies item dates in a plan ('Auto-schedule every item in a plan', 'Returns the before/after diff and logs a comment on every item that moves', 'shift items'). This creates reversible modifications to task scheduling data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs applyTaskDependencyCascade 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 applyTaskDependencyCascade, this is the rule to start with:
applyTaskDependencyCascade 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 applyTaskDependencyCascade call is checked against it from then on.
Questions about applyTaskDependencyCascade
Auto-schedule every item in a plan so all FS/SS/FF task-dependencies are respected (topological pass, durations preserved). Returns the before/after diff and logs a comment on every item that moves. Use forwardOnly: true to only shift items currently in violation (never pull already-valid items earlier). Use pinnedItemIds to keep specific items at their current dates. Pairs with previewTaskDependencyCascade (same inputs, dry-run). 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.
applyTaskDependencyCascade accepts 3 parameters: planId, forwardOnly, pinnedItemIds. Required: planId. 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 applyTaskDependencyCascade: 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.
applyTaskDependencyCascade 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 applyTaskDependencyCascade 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 applyTaskDependencyCascade. 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.
applyTaskDependencyCascade 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