Check RC Method progress. Read-only, safe to call anytime. Returns: current phase (1-8), gate statuses (approved/pending/rejected), saved artifacts list, and UX score if scored. Use this to orient yourself when resuming a session, when the user asks
AI agents call rc_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 tool retrieves and queries the current state of an RC Method pipeline progress (phase, gate statuses, artifacts, scores). It performs no side effects, creates no data, executes no operations, and cannot modify or delete anything. It is purely informational for session orientation, making it a straightforward Read operation with minimal risk even if called by an agent without constraints.
From the tool's definition Tool description explicitly states 'Read-only, safe to call anytime' and 'Returns: current phase, gate statuses, saved artifacts list, and UX score'. The verb 'Check' and 'Returns' indicate data retrieval with no modifications.
Attacks that exploit this kind of access
Check RC Method progress. Read-only, safe to call anytime. Returns: current phase (1-8), gate statuses (approved/pending/rejected), saved artifacts list, and UX score if scored. Use this to orient yourself when resuming a session, when the user asks. 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 rc_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.
rc_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 rc_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 rc_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.
rc_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.
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 →