listTaskDependencies
List FS/SS/FF task-dependency edges in a plan (the Gantt arrows). Scope by planId, projectId, or itemId. direction: 'predecessors' | 'successors' | 'both' (default, only with itemId).
This record as markdown: /tools/io-stablebaseline-sb/listtaskdependencies.md
What listTaskDependencies does on Stable Baseline
AI agents call listTaskDependencies to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
itemId | string | — | Limit to one item's edges. |
planId | string | — | Limit to one plan. |
direction | string | — | Only meaningful with itemId. Default: both. |
projectId | string | — | Limit to one project (all plans). |
Parameters from the server's own tool schema.
Why listTaskDependencies is rated Low
This tool queries and returns existing task dependency relationships without side effects. It is a straightforward read operation on plan/project metadata. The blast radius of misuse is minimal—an agent could only access task dependency data it is already scoped to view. No data is created, modified, deleted, or executed as a result of calling this tool.
From the tool's definition Tool name 'listTaskDependencies' and description 'List FS/SS/FF task-dependency edges in a plan' indicate a query/retrieval operation. No modification, deletion, execution, or financial action is mentioned.
Attacks that exploit this kind of access
The rule that runs listTaskDependencies 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 listTaskDependencies, this is the rule to start with:
listTaskDependencies is read-only, so it stays allowed. 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 listTaskDependencies call is checked against it from then on.
Questions about listTaskDependencies
List FS/SS/FF task-dependency edges in a plan (the Gantt arrows). Scope by planId, projectId, or itemId. direction: 'predecessors' | 'successors' | 'both' (default, only with itemId). It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listTaskDependencies accepts 4 parameters: itemId, planId, direction, projectId. 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 listTaskDependencies: 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.
listTaskDependencies is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listTaskDependencies 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 listTaskDependencies. 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.
listTaskDependencies 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