GIT MCP SERVER TOOLS

33 tools from the Git MCP Server MCP Server, categorised by risk level.

READ 20 tools
Read get_current_user_info Get current user information directly from platform API Read get_fork_info Get fork information for a repository Read get_issue_by_url Get issue details by URL. Supports GitLab and GitHub URLs. Read get_issue_details Get detailed information about a specific issue including comments Read get_merge_request_commits get_merge_request_commits Read get_merge_request_details Get detailed information about a specific merge request Read get_merge_request_diff get_merge_request_diff Read get_platform_config Get configuration information for a specific platform Read get_project_details Get detailed information about a specific project Read list_all_issues List issues across all projects (global search). No project_id needed. Read list_forks List forks of a repository Read list_issues List issues in a project. State can be 'opened', 'closed', or 'all' Read list_merge_requests List merge requests in a project. State can be 'opened', 'closed', 'merged', or 'all' Read list_milestones List milestones for a project. State can be 'active', 'closed', or 'all' Read list_my_issues List issues assigned to me across all projects. Read list_my_merge_requests List merge requests created by the current user (automatically uses configured username) Read list_platforms List all configured Git platforms (GitLab, GitHub, etc.) Read list_projects List projects from a specified Git platform Read refresh_platform_username Refresh username for a configured platform by fetching from token Read test_platform_connection Test connection to a configured platform

Route Git MCP Server through PolicyLayer and every one of its 33 tools is checked against your policy before it runs.

CHECK YOUR STACK →

See every tool, the dangerous ones, and the token cost across your stack.

How many tools does the Git MCP Server MCP server have? +

The Git MCP Server MCP server exposes 33 tools across 3 categories: Read, Write, Destructive.

How do I enforce policies on Git MCP Server tools? +

Route the Git MCP Server server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Git MCP Server tools fall into? +

Git MCP Server tools are categorised as Read (20), Write (11), Destructive (2). Each category has a recommended default policy.

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.

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.