git_remote_list

Lists all remote repositories

SERVERGitHub MCP Server SOURCE0xshariq/github-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xshariq-github-mcp-server/git-remote-list.md

WHAT IT DOES

What git_remote_list does on GitHub MCP Server

AI agents call git_remote_list to retrieve information from GitHub MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why git_remote_list is rated Low

This tool performs a read-only operation—listing remote repositories—which is a standard Git query that returns existing configuration data. There are no side effects, no data modifications, and no code execution. The blast radius of misuse is minimal since an agent listing remotes cannot cause harm beyond revealing repository configuration details.

From the tool's definition Tool name 'git_remote_list' and description 'Lists all remote repositories' indicate a query operation that retrieves configuration data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_remote_list safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_remote_list, this is the rule to start with:

git_remote_list Allowed

git_remote_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_remote_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GitHub MCP Server, apply this rule, and every git_remote_list call is checked against it from then on.

FAQ

Questions about git_remote_list

What does the git_remote_list tool do? +

Lists all remote repositories. It is categorised as a Read tool in the GitHub MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on git_remote_list? +

Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for git_remote_list: 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_list? +

git_remote_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit git_remote_list? +

Yes. Add a rate_limit block to the git_remote_list 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_list completely? +

Set action: deny in the PolicyLayer policy for git_remote_list. 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_list? +

git_remote_list 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.

KEEP EXPLORING

More on GitHub MCP Server, and thousands of servers like it.

This server

All 33 GitHub MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →claude_git_status on Claude Bridge →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →