Removes a dependency relationship between two codebases.
AI agents call remove_codebase_dependency to permanently remove resources in Python Codebase Analysis RAG System — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool removes/deletes an existing relationship between codebases. This is an irreversible deletion of a dependency link. While it doesn't delete code or files themselves, removing a recorded dependency relationship is a destructive action that cannot be automatically undone. Severity is medium because the blast radius is limited to metadata/relationship records rather than actual code.
From the tool's definition 'Removes a dependency relationship between two codebases'
Attacks that exploit this kind of access
Removes a dependency relationship between two codebases. It is categorised as a Destructive tool in the Python Codebase Analysis RAG System MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Python Codebase Analysis RAG System MCP server in PolicyLayer and add a rule for remove_codebase_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 Python Codebase Analysis RAG System. Nothing to install.
remove_codebase_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_codebase_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_codebase_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_codebase_dependency is provided by the Python Codebase Analysis RAG System MCP server (shervinemp/codebasemcp). 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 →