coding_repo_remove
Detach a repo from a coding instance — the counterpart to coding_repo_add, and the way to clean up a binding that was added in error or whose local checkout no longer exists. Identify the repo by
This record as markdown: /tools/io-github-proagentstore-platform/coding-repo-remove.md
What coding_repo_remove does on ProAgentStore
AI agents call coding_repo_remove 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 coding_repo_remove is rated Critical
Removes repository bindings irreversibly from coding instances; cannot be undone without re-adding.
From the tool's definition Detach a repo from a coding instance; clean up a binding.
Attacks that exploit this kind of access
The rule that runs coding_repo_remove 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 coding_repo_remove, this is the rule to start with:
coding_repo_remove 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 coding_repo_remove call is checked against it from then on.
Questions about coding_repo_remove
Detach a repo from a coding instance — the counterpart to coding_repo_add, and the way to clean up a binding that was added in error or whose local checkout no longer exists. Identify the repo by. 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 coding_repo_remove: 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.
coding_repo_remove 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 coding_repo_remove 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 coding_repo_remove. 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.
coding_repo_remove 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