Medium Risk

gitea_create_repo

Create a new repository owned by the token user

How to control gitea_create_repo ↓

What gitea_create_repo does on Crow

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

Medium Risk

Why gitea_create_repo needs a policy

This tool creates a persistent resource (a Git repository) in a version control system. While creation itself is reversible (the repository can be deleted), it modifies the state of the Gitea server, commits resources (disk space, configuration), and could be misused to spam or exhaust resources.

From the tool's definition Tool explicitly creates a new repository owned by the token user. The verb 'create' and the phrase 'new repository' confirm resource creation, which is a write operation.

Documented attack patterns abuse exactly the kind of access gitea_create_repo gives an agent:

How to control gitea_create_repo

PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for gitea_create_repo:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "gitea_create_repo": {
      "limits": [
        {
          "counter": "gitea_create_repo_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

gitea_create_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.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about gitea_create_repo

What does the gitea_create_repo tool do? +

Create a new repository owned by the token user. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on gitea_create_repo? +

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

What risk level is gitea_create_repo? +

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

Can I rate-limit gitea_create_repo? +

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

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

gitea_create_repo is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Crow tool call.

Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

576 Crow 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.