github_update_repo · MCP Toolkit MCP: Risk & Policy

WHAT IT DOES

What github_update_repo does on MCP Toolkit

AI agents use github_update_repo to create or update resources in MCP Toolkit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Toolkit environment.

WHY IT NEEDS A POLICY

Why github_update_repo needs a policy

This tool creates or modifies repository settings on GitHub, which are reversible changes. It does not delete data (would be Destructive) or execute arbitrary code (would be Execute). However, the severity is high because misconfigured repository settings by an AI agent could expose sensitive information, change access controls, or affect collaboration workflows.

From the tool's definition Tool name 'github_update_repo' and description '更新GitHub仓库的设置' (Updates GitHub repository settings) indicates modification of repository configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

github_update_repo Rate-limited

github_update_repo stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "github_update_repo": {
      "limits": [
        {
          "counter": "github_update_repo_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about github_update_repo

What does the github_update_repo tool do? +

更新GitHub仓库的设置。. It is categorised as a Write tool in the MCP Toolkit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on github_update_repo? +

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

What risk level is github_update_repo? +

github_update_repo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit github_update_repo? +

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

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

github_update_repo is provided by the MCP Toolkit MCP server (zxfgds/mcp-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.