git_steer_pr_merge · Git Steer MCP: Risk & Policy

WHAT IT DOES

What git_steer_pr_merge does on Git Steer

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

Merging a PR is a write operation that modifies the repository's codebase and history irreversibly in the sense that it cannot be undone without additional operations. However, it is not Destructive because the action is reversible (via revert commits), and it does not delete data. It is not Execute because merging is a source control operation, not arbitrary code execution.

From the tool's definition Tool name explicitly states 'merge' which modifies repository state by combining branches. Description: 'Merge a pull request' directly describes a write/modification action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_steer_pr_merge Rate-limited

git_steer_pr_merge 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_pr_merge": {
      "limits": [
        {
          "counter": "git_steer_pr_merge_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_pr_merge

What does the git_steer_pr_merge tool do? +

Merge a pull request. 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_pr_merge? +

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

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

Can I rate-limit git_steer_pr_merge? +

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

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

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