Critical Risk →

delete_story_dependency

Deletes an existing dependency relationship between user stories.

How to control delete_story_dependency ↓

What delete_story_dependency does on Snow

AI agents call delete_story_dependency to permanently remove resources in Snow — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_story_dependency needs a policy

This tool performs an irreversible deletion operation that cannot be easily undone. While the blast radius is limited to project management relationships rather than critical data loss, deletion operations that destroy existing connections between work items qualify as Destructive.

From the tool's definition Tool name contains 'delete' and description states 'Deletes an existing dependency relationship between user stories.' The action irreversibly removes a data relationship.

Documented attack patterns abuse exactly the kind of access delete_story_dependency gives an agent:

How to control delete_story_dependency

PolicyLayer is an MCP gateway — it sits between your AI agents and Snow, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_story_dependency:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_story_dependency"
  ]
}

delete_story_dependency disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Snow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_story_dependency

What does the delete_story_dependency tool do? +

Deletes an existing dependency relationship between user stories. It is categorised as a Destructive tool in the Snow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_story_dependency? +

Register the Snow MCP server in PolicyLayer and add a rule for delete_story_dependency: 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 Snow. Nothing to install.

What risk level is delete_story_dependency? +

delete_story_dependency is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_story_dependency? +

Yes. Add a rate_limit block to the delete_story_dependency 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.

How do I block delete_story_dependency completely? +

Set action: deny in the PolicyLayer policy for delete_story_dependency. 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.

What MCP server provides delete_story_dependency? +

delete_story_dependency is provided by the Snow MCP server (shunyaai/snow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Snow tool call.

Start from Snow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

88 Snow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.