Удаляет репозиторий из списка индексации (данные сохраняются в индексе).
AI agents call remove_repo to permanently remove resources in Booster MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a repository from indexing, which is an irreversible operation that cannot be undone without re-adding and re-indexing the repository. While the indexed data may be retained separately, the removal action itself is destructive in nature—it eliminates the repository from the active system.
From the tool's definition Tool name 'remove_repo' combined with description 'Removes repository from indexation list' indicates irreversible deletion of a repository from an active system.
Attacks that exploit this kind of access
Удаляет репозиторий из списка индексации (данные сохраняются в индексе). It is categorised as a Destructive tool in the Booster MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Booster 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 Booster MCP. 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 Booster MCP server (neuroghostdev/booster_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 →