list_forks

THE RISK

Low Risk

Why list_forks needs a policy

This tool retrieves information about repository forks without creating, modifying, or deleting any data. It is a purely informational query with no blast radius if misused by an AI agent, making it a Read category risk with low severity.

From the tool's definition Tool name is 'list_forks' and description states 'List forks of a repository' — a straightforward data retrieval operation with no modification or side effects.

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

POLICY

How to control list_forks

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 list_forks:

policy.json

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

list_forks 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 delete_project Delete a project from the specified platform Destructive close_merge_request close_merge_request Write close_issue Close an issue Write close_milestone Close a milestone Write create_fork create_fork Write create_issue Create a new issue in a project Write create_issue_comment Create a comment on an issue Write create_merge_request create_merge_request

All 33 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 list_forks

What does the list_forks tool do? +

List forks of a repository. 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 list_forks? +

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

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

Can I rate-limit list_forks? +

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

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

list_forks is provided by the Git MCP Server MCP server (yumeminami/git_mcp). 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 →