pr.enableAutoMerge · Promethean OS MCP: Risk & Policy

WHAT IT DOES

What pr.enableAutoMerge does on Promethean OS MCP

AI agents use pr.enableAutoMerge to create or update resources in Promethean OS MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Promethean OS MCP environment.

WHY IT NEEDS A POLICY

Why pr.enableAutoMerge needs a policy

Enabling auto-merge is a Write operation: it changes PR configuration state but does not execute code, delete resources, or move money. The severity is medium because a compromised agent could enable auto-merge on PRs containing malicious code, bypassing review processes, but the action itself is reversible and does not immediately execute arbitrary code or destroy data.

From the tool's definition Tool name 'pr.enableAutoMerge' and description 'Enable auto-merge for a clean PR' indicate a state-modification action on a GitHub pull request resource. This modifies PR settings (enabling auto-merge) but is reversible (auto-merge can be disabled).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pr.enableAutoMerge Rate-limited

pr.enableAutoMerge 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": {
    "pr.enableAutoMerge": {
      "limits": [
        {
          "counter": "pr.enableautomerge_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 Promethean OS MCP, so you can run agents against it safely.

FAQ

Questions about pr.enableAutoMerge

What does the pr.enableAutoMerge tool do? +

Enable auto-merge for a clean PR. It is categorised as a Write tool in the Promethean OS MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pr.enableAutoMerge? +

Register the Promethean OS MCP server in PolicyLayer and add a rule for pr.enableAutoMerge: 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 Promethean OS MCP. Nothing to install.

What risk level is pr.enableAutoMerge? +

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

Can I rate-limit pr.enableAutoMerge? +

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

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

pr.enableAutoMerge is provided by the Promethean OS MCP server (octave-commons/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.