git_remote_remove

Removes a remote repository

Server GitHub MCP Server 0xshariq/github-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What git_remote_remove does on GitHub MCP Server

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.

Why git_remote_remove needs a policy

Removing a remote repository configuration is a destructive, irreversible action. Once the remote is removed, all associated tracking branches and remote references are deleted. This cannot be undone without manually re-adding the remote and re-fetching its data, making it a Destructive category with high severity since it could disrupt CI/CD pipelines, collaboration workflows, and deployment configurations.

From the tool's definition 'Removes a remote repository' - the word 'removes' indicates an irreversible deletion of a configured remote reference

Questions about git_remote_remove

What does the git_remote_remove tool do? +

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.

How do I enforce a policy on git_remote_remove? +

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.

What risk level is git_remote_remove? +

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.

Can I rate-limit git_remote_remove? +

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.

How do I block git_remote_remove completely? +

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.

What MCP server provides git_remote_remove? +

git_remote_remove is provided by the GitHub MCP Server MCP server (0xshariq/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

git_remote_remove is one line of GitHub MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.