fabric_git_merge_pull_request · Git Steer MCP: Risk & Policy

WHAT IT DOES

What fabric_git_merge_pull_request does on Git Steer

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

Merging a pull request integrates code changes into a target branch, which is a significant write operation. While technically reversible via revert commits, the merge itself modifies repository history and branch state. This can have high blast radius if the wrong PR is merged into a protected branch, potentially introducing breaking changes, security vulnerabilities, or disrupting CI/CD pipelines.

From the tool's definition Merge a pull request

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fabric_git_merge_pull_request Rate-limited

fabric_git_merge_pull_request 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": {
    "fabric_git_merge_pull_request": {
      "limits": [
        {
          "counter": "fabric_git_merge_pull_request_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 fabric_git_merge_pull_request

What does the fabric_git_merge_pull_request tool do? +

[git-fabric] 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 fabric_git_merge_pull_request? +

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

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

Can I rate-limit fabric_git_merge_pull_request? +

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

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

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