Create a new repository owned by the token user
AI agents use forgejo_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.
Creating a repository is a write operation that generates new persistent data. While reversible (repositories can be deleted), it commits resources and could enable malicious actors to create numerous repositories for spam, phishing, or to clutter an instance.
From the tool's definition Tool name contains 'create' and description states 'Create a new repository' — this is a reversible write operation that creates a new resource in Forgejo (a Git hosting platform).
Documented attack patterns abuse exactly the kind of access forgejo_create_repo gives an agent:
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 forgejo_create_repo:
{
"version": "1",
"default": "deny",
"tools": {
"forgejo_create_repo": {
"limits": [
{
"counter": "forgejo_create_repo_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}forgejo_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.
Free to start. No card required.
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.
Register the Crow MCP server in PolicyLayer and add a rule for forgejo_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.
forgejo_create_repo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the forgejo_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.
Set action: deny in the PolicyLayer policy for forgejo_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.
forgejo_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.
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.