postrc_override · RC Engine MCP: Risk & Policy

WHAT IT DOES

What postrc_override does on RC Engine

AI agents use postrc_override to create or update resources in RC Engine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RC Engine environment.

WHY IT NEEDS A POLICY

Why postrc_override needs a policy

This tool overrides security/quality scan findings and creates audit records, which is a write operation that modifies the state of the validation pipeline. While it creates an 'immutable' audit record (so not destructive in that sense), it bypasses blocking findings which could allow risky or non-compliant products to ship.

From the tool's definition Override a specific scan finding when the user accepts the risk... Creates an immutable audit record... Use when postrc_gate is blocked by a finding the user wants to accept.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

postrc_override Rate-limited

postrc_override 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": {
    "postrc_override": {
      "limits": [
        {
          "counter": "postrc_override_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 RC Engine, so you can run agents against it safely.

FAQ

Questions about postrc_override

What does the postrc_override tool do? +

[Pro] Override a specific scan finding when the user accepts the risk. Requires: finding_id (from postrc_scan results) and justification (why this is acceptable). Creates an immutable audit record. Use when postrc_gate is blocked by a finding the user wants to accept. ALWAYS warn the user if overriding critical/high severity - explain the risk in plain language. Optionally set an expiration date. After override: re-run postrc_gate to re-evaluate ship decision. It is categorised as a Write tool in the RC Engine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on postrc_override? +

Register the RC Engine MCP server in PolicyLayer and add a rule for postrc_override: 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 RC Engine. Nothing to install.

What risk level is postrc_override? +

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

Can I rate-limit postrc_override? +

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

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

postrc_override is provided by the RC Engine MCP server (originalrashmi/rc-engine-product-framework). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.