Gitea MCP Tool

22 tools. 5 can modify or destroy data without limits.

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

Last updated:

5 can modify or destroy data
17 read-only
22 tools total

Community server · catalogue entry verified 28/06/2026

How to control Gitea MCP Tool ↓

What Gitea MCP Tool exposes to your agents

Read (17) Write / Execute (5) Destructive / Financial (0)
High Risk

The most dangerous Gitea MCP Tool tools

5 of Gitea MCP Tool's 22 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Gitea MCP Tool

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

Rate limit write operations
{
  "gitea_context_set": {
    "limits": [
      {
        "counter": "gitea_context_set_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "gitea_compliance_check_all": {
    "limits": [
      {
        "counter": "gitea_compliance_check_all_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 Gitea MCP Tool — 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 GITEA MCP TOOL →

Instant setup, no code required.

All 22 Gitea MCP Tool tools

READ 17 tools
Read gitea_compliance_check_all Run comprehensive compliance check on branch, commits, and/or PR. Returns detailed report. Read gitea_compliance_check_branch Check if branch name complies with naming conventions. Returns compliance status and suggestions. Read gitea_compliance_check_commit Check if commit message complies with Conventional Commit format. Can check by SHA or message directly. Read gitea_compliance_check_pr Check if PR description complies with format requirements (sections, issue links, etc.). Read gitea_compliance_init Initialize compliance configuration file (.gitea/compliance.yaml) with default rules. Read gitea_context_get Get current default context (owner, repo, org, project) Read gitea_init Initialize project configuration files (.gitea-mcp.json). Auto-detects Git repository info if available. Read gitea_mcp_upgrade Upgrade Gitea MCP tool to the latest version. Downloads and installs from the latest release. Read gitea_user_current Get information about the currently authenticated user Read gitea_workflow_check_blocked Detect issues that are blocked or exceeding SLA. Checks for stale issues based on priority-specific time limit Read gitea_workflow_check_issues Check all open issues against workflow rules. Identifies missing labels, conflicts, and provides suggestions f Read gitea_workflow_escalate_priority Automatically escalate priority for aged issues. P3→P2 after 30 days, P2→P1 after 14 days, P1→P0 after 3 days. Read gitea_workflow_infer_labels Infer labels for an issue based on title and body content. Uses keyword matching and pattern recognition to su Read gitea_workflow_init Initialize Issue workflow configuration for a project. Generates .gitea/issue-workflow.yaml with labels, board Read gitea_workflow_load_config Load and parse the workflow configuration from .gitea/issue-workflow.yaml. Returns the parsed config and valid Read gitea_workflow_sync_labels Sync repository labels based on workflow configuration. Creates status/, priority/, type/ and other labels def Read gitea_workflow_sync_status Synchronize issue status labels with project board column positions. Supports label-to-board, board-to-label,

Questions about Gitea MCP Tool

How do I prevent bulk modifications through Gitea MCP Tool? +

The Gitea MCP Tool server has 5 write tools including gitea_context_set, gitea_issue_create, gitea_pr_create. 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 Gitea MCP Tool.

How many tools does the Gitea MCP Tool MCP server expose? +

22 tools across 2 categories: Read, Write. 17 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on Gitea MCP Tool? +

Register the Gitea MCP Tool 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 Gitea MCP Tool tool call.

Deterministic rules across all 22 Gitea MCP Tool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

22 Gitea MCP Tool tools catalogued and risk-classified — across an index of 43,000+ 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.