remove_dependency
AI agents call remove_dependency to permanently remove resources in Service Atlas MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name 'remove_dependency' strongly suggests irreversible deletion or removal of dependency relationships from the service mapping system. While the description is empty (lowering confidence slightly), the semantic meaning of 'remove' in the context of a dependency management system indicates a destructive action that cannot be undone.
From the tool's definition Tool name 'remove_dependency' indicates deletion/removal of service dependency records. The verb 'remove' combined with the context of dependency mapping data suggests irreversible deletion of relationship data.
Attacks that exploit this kind of access
remove_dependency. It is categorised as a Destructive tool in the Service Atlas MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Service Atlas MCP Server MCP server in PolicyLayer and add a rule for remove_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 Service Atlas MCP Server. Nothing to install.
remove_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 remove_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 remove_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.
remove_dependency is provided by the Service Atlas MCP Server MCP server (service-atlas/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →