dismissTaskDependencyReview
Per-item: clear needs_dependency_review without changing dates — keeps the edge, ignores the suggestion. Use when the successor should stay put despite the predecessor shifting.
This record as markdown: /tools/io-stablebaseline-sb/dismisstaskdependencyreview.md
What dismissTaskDependencyReview does on Stable Baseline
AI agents use dismissTaskDependencyReview 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 |
|---|---|---|---|
improvementId | string | Yes |
Parameters from the server's own tool schema.
Why dismissTaskDependencyReview is rated Medium
This tool modifies a flag/status on a task dependency review item (clearing the `needs_dependency_review` marker) without deleting data or executing code. It is a reversible state change — the edge is kept and dates are unchanged — making it a Write operation. Misuse has minimal blast radius as it only suppresses a review prompt on a single task dependency.
From the tool's definition clear `needs_dependency_review` without changing dates — keeps the edge, ignores the suggestion
Attacks that exploit this kind of access
The rule that runs dismissTaskDependencyReview 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 dismissTaskDependencyReview, this is the rule to start with:
dismissTaskDependencyReview 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 dismissTaskDependencyReview call is checked against it from then on.
Questions about dismissTaskDependencyReview
Per-item: clear needs_dependency_review without changing dates — keeps the edge, ignores the suggestion. Use when the successor should stay put despite the predecessor shifting. 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.
dismissTaskDependencyReview accepts 1 parameter: improvementId. Required: improvementId. 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 dismissTaskDependencyReview: 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.
dismissTaskDependencyReview 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 dismissTaskDependencyReview 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 dismissTaskDependencyReview. 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.
dismissTaskDependencyReview 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