gh_api · GitHub CLI MCP Server MCP: Risk & Policy

WHAT IT DOES

What gh_api does on GitHub CLI MCP Server

AI agents invoke gh_api to trigger actions in GitHub CLI MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why gh_api needs a policy

This tool wraps the GitHub CLI to make arbitrary authenticated API requests. It can perform any GitHub API operation depending on the arguments passed — including reads, writes, deletions, and administrative actions. Since the tool's effects are entirely argument-dependent and can span from read-only to destructive (e.g., deleting repos, force-pushing, removing users), it must be classified as Execute at minimum.

From the tool's definition Make an authenticated GitHub API request

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gh_api Rate-limited

gh_api stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gh_api": {
      "limits": [
        {
          "counter": "gh_api_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GitHub CLI MCP Server, so you can run agents against it safely.

FAQ

Questions about gh_api

What does the gh_api tool do? +

Make an authenticated GitHub API request. It is categorised as a Execute tool in the GitHub CLI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on gh_api? +

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

What risk level is gh_api? +

gh_api is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit gh_api? +

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

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

gh_api is provided by the GitHub CLI MCP Server MCP server (munch-group/gh-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.