[Pro] Final checkpoint - ship/no-ship decision. Call after postrc_scan completes and user has reviewed findings. NEVER auto-approve - always present findings summary first. Returns PASS (safe to ship), WARN (issues exist but not blocking), or BLOCK (critical issues must be fixed or overridden). I...
AI agents invoke postrc_gate to trigger actions in RC Engine. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a critical control gate that affects product release decisions and pipeline state. While not directly destructive or financial, it triggers operational consequences (shipping a product, overriding safety checks) whose effects depend on the decision logic and are not easily reversible once a product ships.
From the tool's definition Tool makes a final ship/no-ship decision with outcomes PASS, WARN, or BLOCK that determine pipeline progression.
Attacks that exploit this kind of access
[Pro] Final checkpoint - ship/no-ship decision. Call after postrc_scan completes and user has reviewed findings. NEVER auto-approve - always present findings summary first. Returns PASS (safe to ship), WARN (issues exist but not blocking), or BLOCK (critical issues must be fixed or overridden). If BLOCK: user must either fix issues and re-scan, or use postrc_override to accept risks. After PASS/approved: pipeline is complete for the build phase. Consider running trace_map_findings next for coverage metrics. It is categorised as a Execute tool in the RC Engine MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the RC Engine MCP server in PolicyLayer and add a rule for postrc_gate: 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.
postrc_gate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the postrc_gate 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.
Set action: deny in the PolicyLayer policy for postrc_gate. 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.
postrc_gate 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →