// SCAN REPORT

GitHub Kanban MCP Server

4 tools. 3 can modify or destroy data without limits.

3 write tools that can modify data. Rate limits recommended.

Last updated: 12 Jun 2026

3 can modify or destroy data

1 read-only

4 tools total

Community server · catalogue entry verified 12/06/2026

How to control GitHub Kanban MCP Server ↓

TOOL MAP

What GitHub Kanban MCP Server exposes to your agents

Read (1) Write / Execute (3) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous GitHub Kanban MCP Server tools

Write · Medium add_comment Adding comments to GitHub issues creates new, reversible data. Write · Medium create_issue This tool creates new issues in a GitHub repository, which is reversible data modification. Write · Medium update_issue Update operations are reversible writes—changes can be undone by updating again with previous values.

3 of GitHub Kanban MCP Server's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control GitHub Kanban MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub Kanban MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "add_comment": {
    "limits": [
      {
        "counter": "add_comment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "list_issues": {
    "limits": [
      {
        "counter": "list_issues_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register GitHub Kanban MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GITHUB KANBAN →

Free to start. No card required.

FULL CATALOGUE

All 4 GitHub Kanban MCP Server tools

WRITE 3 tools

Write add_comment タスクにコメントを追加 Write create_issue 新しいissueを作成します Write update_issue 既存のissueを更新します

READ 1 tools

Read list_issues カンバンボードのissue一覧を取得します

FAQ

Questions about GitHub Kanban MCP Server

How do I prevent bulk modifications through GitHub Kanban MCP Server? +

The GitHub Kanban MCP Server server has 3 write tools including add_comment, create_issue, update_issue. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach GitHub Kanban MCP Server.

How many tools does the GitHub Kanban MCP Server MCP server expose? +

4 tools across 2 categories: Read, Write. 1 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on GitHub Kanban MCP Server? +

Register the GitHub Kanban MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every GitHub Kanban MCP Server tool call.

Deterministic rules across all 4 GitHub Kanban MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GITHUB KANBAN →

Free to start. No card required.

4 GitHub Kanban MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.