GitHub Projects MCP Server

21 tools. 20 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated:

20 can modify or destroy data
1 read-only
21 tools total

Community server · catalogue entry verified 11/06/2026

How to control GitHub Projects MCP Server ↓

Read (1) Write / Execute (17) Destructive / Financial (3)
Critical Risk

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

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

Deny destructive operations
{
  "delete-project": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "clear-item-field-value": {
    "limits": [
      {
        "counter": "clear-item-field-value_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "get-project-items": {
    "limits": [
      {
        "counter": "get-project-items_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

  1. Create a free account and register GitHub Projects MCP Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON GITHUB PROJECTS →

Free to start. No card required.

Other MCP servers with similar tools — same risk classification, starter policies for each.

Can an AI agent delete data through the GitHub Projects MCP Server MCP server? +

Yes. The GitHub Projects MCP Server server exposes 3 destructive tools including delete-project, delete-project-field, delete-project-item. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

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

The GitHub Projects MCP Server server has 17 write tools including clear-item-field-value, add-draft-issue, add-item-to-project. 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 Projects MCP Server.

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

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

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

Register the GitHub Projects 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 Projects MCP Server tool call.

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

Free to start. No card required.

21 GitHub Projects MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.