oomkill_remediate · Git Steer MCP: Risk & Policy

WHAT IT DOES

What oomkill_remediate does on Git Steer

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

This tool creates a Pull Request in a GitOps repository to modify Kubernetes resource limits. Creating a PR is a reversible write operation — it does not directly merge or apply changes, and PR deduplication further suggests controlled, reviewable modifications. It does not execute code, delete data, or involve financial transactions.

From the tool's definition Auto-bump resource limits for OOMKilled pods by creating a PR to the GitOps repo

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

oomkill_remediate Rate-limited

oomkill_remediate 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": {
    "oomkill_remediate": {
      "limits": [
        {
          "counter": "oomkill_remediate_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 oomkill_remediate

What does the oomkill_remediate tool do? +

Auto-bump resource limits for OOMKilled pods by creating a PR to the GitOps repo. Calculates new limits as a multiplier of current limits (default: 1.5x). Uses PR dedup to avoid duplicate remediation PRs. 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 oomkill_remediate? +

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

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

Can I rate-limit oomkill_remediate? +

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

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

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