Check traceability coverage. Read-only, safe to call anytime after trace_enhance_prd. Returns: total requirements, implemented count, verified count, coverage percentages, orphan lists. Use when user asks
AI agents call trace_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 traceability metrics without modifying any data. It has no side effects and is safe to invoke repeatedly. It fits the Read category definition: 'retrieves or queries data; no side effects'.
From the tool's definition Tool is explicitly described as 'Read-only' and 'safe to call anytime'. It returns status information: 'total requirements, implemented count, verified count, coverage percentages, orphan lists'. No modifications, deletions, or side effects are performed.
Attacks that exploit this kind of access
Check traceability coverage. Read-only, safe to call anytime after trace_enhance_prd. Returns: total requirements, implemented count, verified count, coverage percentages, orphan lists. Use when 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 trace_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.
trace_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 trace_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 trace_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.
trace_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 →