Remove a repository from the status bar by its label.
AI agents call remove_repo to permanently remove resources in Agentic Bits Claude Plugin — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool removes a repository entry from the configuration. This is a deletion operation that removes tracked repository data. While it doesn't delete the actual git repository on disk, it irreversibly removes the repository's configuration/tracking entry from the status bar. The action is not easily reversible without re-adding and reconfiguring the repository, making it Destructive rather than Write.
From the tool's definition Remove a repository from the status bar by its label
Attacks that exploit this kind of access
Remove a repository from the status bar by its label. It is categorised as a Destructive tool in the Agentic Bits Claude Plugin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Agentic Bits Claude Plugin MCP server in PolicyLayer and add a rule for remove_repo: 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 Agentic Bits Claude Plugin. Nothing to install.
remove_repo 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_repo 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_repo. 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_repo is provided by the Agentic Bits Claude Plugin MCP server (onesmartguy/agentic-bits-claude-plugin). 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 →