config_add_repo · Git Steer MCP: Risk & Policy

WHAT IT DOES

What config_add_repo does on Git Steer

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

This is a Write operation because it creates or modifies configuration data (adding a repository to a managed list). It is reversible—a repository can be removed from the managed list. Severity is medium rather than high because the blast radius is limited to configuration scope (which repos are managed); it does not directly execute destructive operations, trigger workflows, or move financial resources.

From the tool's definition Tool adds a repository to a managed repos configuration. The name 'config_add_repo' and description 'Add a repository to managed repos' indicate creation/modification of configuration state that controls which repositories are subject to autonomous GitHub…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

config_add_repo Rate-limited

config_add_repo 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": {
    "config_add_repo": {
      "limits": [
        {
          "counter": "config_add_repo_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 config_add_repo

What does the config_add_repo tool do? +

Add a repository to managed repos. 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 config_add_repo? +

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

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

Can I rate-limit config_add_repo? +

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

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

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