git_worktree_list

A read tool on the GitHub MCP server.

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

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/io-github-aifity-omnigit-mcp/git-worktree-list.md

WHAT IT DOES

What git_worktree_list does on GitHub

AI agents call git_worktree_list to retrieve information from GitHub 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_worktree_list is rated Low

This tool performs a read-only query operation to enumerate git worktrees. It has no side effects, does not modify any data, and simply retrieves existing state information. This is a benign operation with minimal security risk.

From the tool's definition Tool name is 'git_worktree_list' and description is 'Git worktree list'. The 'list' operation retrieves and displays information about git worktrees without modifying any data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_worktree_list safely

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

git_worktree_list Allowed

git_worktree_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_worktree_list": {}
  }
}

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

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

FAQ

Questions about git_worktree_list

What does the git_worktree_list tool do? +

git_worktree_list is a read tool on the GitHub MCP server. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on git_worktree_list? +

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

What risk level is git_worktree_list? +

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

Can I rate-limit git_worktree_list? +

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

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

git_worktree_list is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub 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 →