remote_list

THE RISK

Low Risk

Why remote_list needs a policy

This tool retrieves and displays Git remote information without creating, modifying, or deleting any data. It has no side effects and is a standard read-only Git operation. Even if an AI agent misuses it, listing remotes poses negligible security risk.

From the tool's definition Tool name is 'remote_list' and description states 'List remotes' - a pure query operation that retrieves remote repository configuration without modification.

Documented attack patterns abuse exactly the kind of access remote_list gives an agent:

POLICY

How to control remote_list

PolicyLayer is an MCP gateway — it sits between your AI agents and Git MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for remote_list:

policy.json

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

remote_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Git MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Git MCP Server tools

Destructive branch_delete Delete a branch Destructive remote_remove Remove a remote Destructive stash_pop Apply and remove a stash Destructive tag_delete Delete a tag Execute bulk_action Execute multiple Git operations in sequence. This is the preferred way to execute multiple Execute checkout Switch branches or restore working tree files Write add Stage files Write branch_create Create a new branch

All 21 Git MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about remote_list

What does the remote_list tool do? +

List remotes. It is categorised as a Read tool in the Git MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on remote_list? +

Register the Git MCP Server MCP server in PolicyLayer and add a rule for 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 Git MCP Server. Nothing to install.

What risk level is remote_list? +

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

Can I rate-limit remote_list? +

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

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

remote_list is provided by the Git MCP Server MCP server (sheshiyer/git-mcp-v2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Git MCP Server tool call.

Start from Git MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →