create_repository
A write tool on the GitHub MCP server.
This record as markdown: /tools/io-github-aifity-omnigit-mcp/create-repository.md
What create_repository does on GitHub
AI agents use create_repository to create or update resources in GitHub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub environment.
Why create_repository is rated Medium
Creating a repository is a write operation that modifies the GitHub organization/user state by adding a new resource. While reversible (repositories can be deleted), this is a high-severity action because it can consume resources, trigger billing, establish new access control surfaces, and potentially interfere with CI/CD pipelines.
From the tool's definition Tool name 'create_repository' and description 'Create repository' directly indicate creation of a new repository resource on GitHub, which is a reversible write operation.
Attacks that exploit this kind of access
The rule that runs create_repository safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_repository, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every create_repository call is checked against it from then on.
Questions about create_repository
create_repository is a write tool on the GitHub MCP server. It is categorised as a Write tool in the GitHub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub 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 GitHub. 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 GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue