Create a new repository for the authenticated user
AI agents use create_repo to create or update resources in Forgejo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Forgejo environment.
Creating a repository is a write operation that modifies the state of the Forgejo/Gitea instance by adding a new resource. It is not destructive (the action is reversible), not financial, and not an execute-style operation. The severity is medium because while repository creation is a persistent change, it does not have the blast radius of destructive operations or actions affecting multiple users/systems.
From the tool's definition Tool description states 'Create a new repository' — this creates new data (a repository) in a reversible manner. The authenticated user can delete or modify the repository after creation.
Documented attack patterns abuse exactly the kind of access create_repo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Forgejo, and nothing reaches the server without passing your rules. This is the rule we recommend for create_repo:
{
"version": "1",
"default": "deny",
"tools": {
"create_repo": {
"limits": [
{
"counter": "create_repo_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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 for the authenticated user. It is categorised as a Write tool in the Forgejo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Forgejo MCP server in PolicyLayer and add a rule for 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 Forgejo. Nothing to install.
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 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 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.
create_repo is provided by the Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Forgejo, 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.
103 Forgejo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.