AI agents use create_repository to create or update resources in Gitea MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitea MCP Server environment.
Creating a repository is a reversible write operation that adds a new resource to the Gitea instance. It does not execute arbitrary code, delete data, or move money. While repository creation could be misused to spam or consume resources, the operation itself is non-destructive and can be undone (repositories can be deleted).
From the tool's definition Tool name 'create_repository' and description 'Create a new repository on Gitea instance' indicate creation of new data/resources. The server description mentions 'creating repositories' as a core capability.
Documented attack patterns abuse exactly the kind of access create_repository gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gitea MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_repository:
{
"version": "1",
"default": "deny",
"tools": {
"create_repository": {
"limits": [
{
"counter": "create_repository_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_repository 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 on Gitea instance. It is categorised as a Write tool in the Gitea MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gitea MCP Server MCP server in PolicyLayer and add a rule for create_repository: 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 Gitea MCP Server. Nothing to install.
create_repository 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_repository 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_repository. 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_repository is provided by the Gitea MCP Server MCP server (mushroomfleet/gitea-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gitea MCP Server, 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.
4 Gitea MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.