AI agents use git_steer_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.
Creating a repository is a reversible write operation—the repository can be deleted afterward. However, severity is high because an autonomous agent creating repositories could lead to resource sprawl, potential cost implications (private repos), namespace pollution, or use of the account's reputation for malicious purposes.
From the tool's definition Tool name 'git_steer_repo_create' and description 'Create a new GitHub repository' indicate creation of a new resource. The server context shows it 'enables control over repositories' through natural language, confirming write capability.
Attacks that exploit this kind of access
Create a new GitHub 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.
Register the Git Steer MCP server in PolicyLayer and add a rule for git_steer_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.
git_steer_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 git_steer_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 git_steer_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.
git_steer_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.
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 →