repo_create · Git Steer MCP: Risk & Policy

WHAT IT DOES

What repo_create does on Git Steer

AI agents use repo_create to create or update resources in Git Steer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Git Steer environment.

WHY IT NEEDS A POLICY

Why repo_create needs a policy

Creating a repository is a Write-category action because it creates new data structures reversibly. However, severity is high because unauthorized repository creation could be used to establish malicious codebases, pollute the organization's namespace, waste resources, or create confusion about the source of code.

From the tool's definition Tool name 'repo_create' and description 'Create a new repository' indicate data creation. This creates a new GitHub repository, which is a reversible write operation (the repository can be deleted later).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

repo_create Rate-limited

repo_create 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "repo_create": {
      "limits": [
        {
          "counter": "repo_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Git Steer, so you can run agents against it safely.

FAQ

Questions about repo_create

What does the repo_create tool do? +

Create a new repository. It is categorised as a Write tool in the Git Steer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on repo_create? +

Register the Git Steer MCP server in PolicyLayer and add a rule for 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 Git Steer. Nothing to install.

What risk level is repo_create? +

repo_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit repo_create? +

Yes. Add a rate_limit block to the 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.

How do I block repo_create completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides repo_create? +

repo_create is provided by the Git Steer MCP server (ry-ops/git-steer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.