Create a new repository
AI agents use gh_repo_create to create or update resources in GitHub CLI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub CLI MCP Server environment.
Creating a repository is a write operation that adds a new resource to GitHub with reversible effects (the repository can be deleted later). While it has significant blast radius in a multi-tenant or organizational context (consumes resources, affects visibility/permissions), it does not irreversibly destroy data (Destructive), execute arbitrary code (Execute), or move money (Financial).
From the tool's definition Tool name 'gh_repo_create' and description 'Create a new repository' indicate creation of a new resource with persistent effects.
Attacks that exploit this kind of access
Create a new repository. It is categorised as a Write tool in the GitHub CLI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub CLI MCP Server MCP server in PolicyLayer and add a rule for gh_repo_create: 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 CLI MCP Server. Nothing to install.
gh_repo_create 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 gh_repo_create 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 gh_repo_create. 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.
gh_repo_create is provided by the GitHub CLI MCP Server MCP server (munch-group/gh-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →