repo_settings · Git Steer MCP: Risk & Policy

WHAT IT DOES

What repo_settings does on Git Steer

AI agents use repo_settings 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_settings needs a policy

The tool modifies repository settings reversibly (settings can be changed again), making it Write rather than Destructive. However, severity is high because repository settings control access permissions, branch protections, security policies, and other critical configurations—misuse could compromise repository integrity, expose secrets, or disable security controls.

From the tool's definition Tool name 'repo_settings' with description 'Update repository settings' indicates modification of repository configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

repo_settings Rate-limited

repo_settings 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_settings": {
      "limits": [
        {
          "counter": "repo_settings_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_settings

What does the repo_settings tool do? +

Update repository settings. 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_settings? +

Register the Git Steer MCP server in PolicyLayer and add a rule for repo_settings: 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_settings? +

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

Can I rate-limit repo_settings? +

Yes. Add a rate_limit block to the repo_settings 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_settings completely? +

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

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