Create a new GitHub repository on a personal account or within an organization
AI agents use create_repo to create or update resources in Gitbridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitbridge environment.
This tool creates a new repository, which is a reversible Write operation. While repository creation can have organizational implications, it does not delete data (Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial).
From the tool's definition Tool name 'create_repo' and description 'Create a new GitHub repository on a personal account or within an organization' indicate creation of a new resource that modifies account state.
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 Gitbridge, 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 GitHub repository on a personal account or within an organization. It is categorised as a Write tool in the Gitbridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gitbridge 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 Gitbridge. 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 Gitbridge MCP server (iotus/gitbridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gitbridge, 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.
16 Gitbridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.