Removes a remote repository
AI agents call git-remote-remove to permanently remove resources in GitHub MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a remote is a destructive, hard-to-reverse operation: it deletes the remote tracking configuration and all associated remote-tracking branches from the local repo. If misused by an AI agent, it could sever the link to the upstream/origin repository, disrupting CI/CD pipelines and collaboration workflows. Recovery requires knowing the original remote URL and re-adding it manually.
From the tool's definition 'Removes a remote repository' — the word 'removes' indicates an irreversible deletion of the remote configuration
Attacks that exploit this kind of access
Removes a remote repository. It is categorised as a Destructive tool in the GitHub MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for git-remote-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 GitHub MCP Server. Nothing to install.
git-remote-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 git-remote-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 git-remote-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.
git-remote-remove is provided by the GitHub MCP Server MCP server (jungchihoon/github-mcp-server). 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 →