git_steer_repo_settings · Git Steer MCP: Risk & Policy

WHAT IT DOES

What git_steer_repo_settings does on Git Steer

AI agents use git_steer_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 git_steer_repo_settings needs a policy

This tool creates or modifies repository metadata reversibly. While 'Update' suggests write operations, the ability to change visibility (public/private) and other settings could have significant blast radius if an AI agent misconfigures a repository—exposing private code or restricting access unintentionally. However, these changes are reversible (can be toggled back), preventing it from being Destructive.

From the tool's definition Tool name 'git_steer_repo_settings' and description 'Update repository settings' explicitly indicates modification of repository configuration including visibility, which affects access control and public/private state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_steer_repo_settings Rate-limited

git_steer_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": {
    "git_steer_repo_settings": {
      "limits": [
        {
          "counter": "git_steer_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 git_steer_repo_settings

What does the git_steer_repo_settings tool do? +

Update repository settings (description, homepage, visibility, etc.). 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 git_steer_repo_settings? +

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

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

Can I rate-limit git_steer_repo_settings? +

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

Set action: deny in the PolicyLayer policy for git_steer_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 git_steer_repo_settings? +

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