[Pro] Run AFTER building (Phase 6 Forge complete). Scans code for security vulnerabilities, checks monitoring instrumentation, and optionally runs legal compliance review (Pro tier - enable via postrc_configure with legal_enabled=true). Pass code_context with the actual project code. Returns find...
AI agents invoke postrc_scan 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 runs active analysis processes (LLM-based code scanning, security vulnerability detection, compliance review) and produces output artifacts. It triggers external operations whose effects depend on the code_context argument. The most severe applicable category is Execute, as it runs analysis pipelines and can generate files (REMEDIATION-TASKS).
From the tool's definition Scans code for security vulnerabilities, checks monitoring instrumentation, and optionally runs legal compliance review... involves LLM analysis... generates REMEDIATION-TASKS file
Attacks that exploit this kind of access
[Pro] Run AFTER building (Phase 6 Forge complete). Scans code for security vulnerabilities, checks monitoring instrumentation, and optionally runs legal compliance review (Pro tier - enable via postrc_configure with legal_enabled=true). Pass code_context with the actual project code. Returns findings by severity (critical/high/medium/low) with CWE/legal references. LONG-RUNNING: involves LLM analysis. After success: present findings to user in plain language. Then call postrc_gate for ship/no-ship decision. If critical findings exist, also generates REMEDIATION-TASKS file. 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_scan: 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_scan 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_scan 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_scan. 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_scan 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 →