PRE-FLIGHT tool - run BEFORE RC Method build phase, ideally after rc_define (Phase 2). Generates an observability requirements document from the PRD: error tracking setup, analytics events, SLO definitions, dashboard specs, and alerting rules. This ensures monitoring is designed in, not bolted on...
AI agents use postrc_generate_observability_spec to create or update resources in RC Engine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RC Engine environment.
This tool creates new specification documents and configuration frameworks (observability requirements, monitoring setup, alerting rules) that guide downstream implementation. While it produces outputs that inform the build phase, it does not directly execute, delete, or modify production systems. The artifact generation is reversible and represents a Write-category action.
From the tool's definition Generates an observability requirements document with error tracking setup, analytics events, SLO definitions, dashboard specs, and alerting rules. Creates and produces structured specification artifacts.
Attacks that exploit this kind of access
PRE-FLIGHT tool - run BEFORE RC Method build phase, ideally after rc_define (Phase 2). Generates an observability requirements document from the PRD: error tracking setup, analytics events, SLO definitions, dashboard specs, and alerting rules. This ensures monitoring is designed in, not bolted on after shipping. Output feeds into rc_architect as a companion to the PRD. Optional but strongly recommended for production applications. It is categorised as a Write tool in the RC Engine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RC Engine MCP server in PolicyLayer and add a rule for postrc_generate_observability_spec: 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_generate_observability_spec is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the postrc_generate_observability_spec 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_generate_observability_spec. 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_generate_observability_spec 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 →