gitea_action

SERVERUnClick SOURCE@unclick/mcp-server

High RISK CLASS

Category Execute

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/gitea-action.md

WHAT IT DOES

What gitea_action does on UnClick

AI agents invoke gitea_action to trigger actions in UnClick. 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.

Parameter	Type	Required	Description
`ref`	string	—	Branch, tag, or commit for get_file or get_commit_status.
`base`	string	—	Pull request base branch.
`body`	string	—	Issue, pull request, or comment body text.
`head`	string	—	Pull request head branch.
`page`	number	—	Page number.
`path`	string	—	Repo-relative file path for get_file and upsert_file.
`repo`	string	—	Repository name.
`owner`	string	—	Repository owner login.
`query`	string	—	Search query string (for search_repos).
`state`	string	—	Filter by state: open, closed, all.
`title`	string	—	Issue or pull request title.
`action`	string	Yes	Action: get_version, search_repos, get_repo, list_branches, create_branch, get_file, get_commit_status, upsert_file, list_issues, create_issue, comment_issue_or

Parameters from the server's own tool schema.

RISK

Why gitea_action is rated High

Tool performs multiple write and execute-level forge operations with broad repository impact.

From the tool's definition create branches, commits, open/merge/close pull requests, manage push mirrors

Risk signalsAccepts file system path (path) · Accepts URL/endpoint input (base_url) · Handles credentials or secrets (access_token) · Accepts raw HTML/template content (body) · High parameter count (39 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gitea_action safely

PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gitea_action, this is the rule to start with:

gitea_action Rate-limited

gitea_action 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": {
    "gitea_action": {
      "limits": [
        {
          "counter": "gitea_action_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every gitea_action call is checked against it from then on.

FAQ

Questions about gitea_action

What does the gitea_action tool do? +

Interact with the self-hosted Gitea forge REST API: read repos, branches, and files, create branches and single-file commits, open/merge/close pull requests, comment, manage issues, and manage push mirrors so the forge owns downstream syncs (for example a calm scheduled mirror to GitHub). It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does gitea_action accept? +

gitea_action accepts 12 parameters: ref, base, body, head, page, path, repo, owner, query, state, title, action. Required: action. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gitea_action? +

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

What risk level is gitea_action? +

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

Can I rate-limit gitea_action? +

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

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

gitea_action is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools → High-risk tools on this server →

Across the catalogue

qt_trigger_action on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →