remove_repo
Remove one indexed repository from a repo-chat instance (by repo_url or owner/repo), or all of them if neither is given. Deletes its vectors and overview.
This record as markdown: /tools/io-github-proagentstore-platform/remove-repo.md
What remove_repo does on ProAgentStore
AI agents call remove_repo to permanently remove resources in ProAgentStore, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_repo is rated Critical
This tool irreversibly deletes repository data from a repo-chat instance. Deletion of indexed repositories and their vector representations cannot be undone. The ability to remove all repositories (when neither parameter is given) amplifies the destructive impact.
From the tool's definition Tool description explicitly states 'Remove', 'Deletes its vectors and overview' — irreversible deletion of indexed repository data and associated vector embeddings.
Attacks that exploit this kind of access
The rule that runs remove_repo safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_repo, this is the rule to start with:
remove_repo 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 ProAgentStore, apply this rule, and every remove_repo call is checked against it from then on.
Questions about remove_repo
Remove one indexed repository from a repo-chat instance (by repo_url or owner/repo), or all of them if neither is given. Deletes its vectors and overview. It is categorised as a Destructive tool in the ProAgentStore MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ProAgentStore 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 ProAgentStore. 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 ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ProAgentStore, and thousands of servers like it.
Across the catalogue