Check Post-RC validation progress. Read-only, safe to call anytime. Returns: active modules, latest scan ID and findings count, override count, and gate status. Use this to orient yourself when resuming a session or when the user asks about validation status. Call before postrc_gate if you need t...
AI agents call postrc_status to retrieve information from RC Engine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure information retrieval tool that queries Post-RC validation status. It has no side effects, cannot modify data, and poses minimal security risk. The 'read-only' designation and emphasis on safety confirm classification as a Read category tool with low severity.
From the tool's definition Tool description explicitly states 'Read-only, safe to call anytime' and 'Returns: active modules, latest scan ID and findings count, override count, and gate status.' The tool retrieves validation progress information without modifying, executing, or…
Attacks that exploit this kind of access
Check Post-RC validation progress. Read-only, safe to call anytime. Returns: active modules, latest scan ID and findings count, override count, and gate status. Use this to orient yourself when resuming a session or when the user asks about validation status. Call before postrc_gate if you need to verify scan results are available. It is categorised as a Read tool in the RC Engine MCP Server, which means it retrieves data without modifying state.
Register the RC Engine MCP server in PolicyLayer and add a rule for postrc_status: 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_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the postrc_status 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_status. 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_status 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.
postrc_status is one line of RC Engine's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →