delete_story_dependency
Remove a story dependency link by its m2m_story_dependencies sys_id. Requires WRITE_ENABLED=true.
This record as markdown: /tools/servicenow-mcp-server/delete-story-dependency.md
What delete_story_dependency does on ServiceNow MCP Server
AI agents call delete_story_dependency to permanently remove resources in ServiceNow MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_story_dependency is rated Critical
Deletes relationship records irreversibly; cannot be undone without manual restoration.
From the tool's definition Remove a story dependency link; irreversible deletion of relationship data.
Attacks that exploit this kind of access
The rule that runs delete_story_dependency safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_story_dependency, this is the rule to start with:
delete_story_dependency is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow MCP Server, apply this rule, and every delete_story_dependency call is checked against it from then on.
Questions about delete_story_dependency
Remove a story dependency link by its m2m_story_dependencies sys_id. Requires WRITE_ENABLED=true. It is categorised as a Destructive tool in the ServiceNow MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ServiceNow MCP Server 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 ServiceNow MCP Server. Nothing to install.
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.
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.
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.
delete_story_dependency is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow MCP Server, and thousands of servers like it.
Across the catalogue