rc_define

Server RC Engine originalrashmi/rc-engine-product-framework

Category Write

Risk class Medium

Parameters 00 required

WHAT IT DOES

What rc_define does on RC Engine

AI agents use rc_define 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.

WHY IT NEEDS A POLICY

Why rc_define needs a policy

The tool creates and saves a PRD file to disk. This is a Write operation — it produces and persists a structured document. There are no destructive, financial, or execution side effects. Severity is low because the output is a planning document with no operational impact.

From the tool's definition Generates a Product Requirements Document...saved to rc-method/prds/

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rc_define Rate-limited

rc_define stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rc_define": {
      "limits": [
        {
          "counter": "rc_define_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches RC Engine, so you can run agents against it safely.

FAQ

Questions about rc_define

What does the rc_define tool do? +

Phase 2 (Define). Generates a Product Requirements Document from user-provided feature descriptions, user stories, and requirements. Produces an 11-section PRD saved to rc-method/prds/. Returns PRD content + gate prompt. Present the PRD to the user for review. Prerequisites: Phase 1 gate approved. After gate approval: moves to Phase 3 (Architect). Consider running ux_score on the feature list and ux_generate for UX-heavy products. 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.

How do I enforce a policy on rc_define? +

Register the RC Engine MCP server in PolicyLayer and add a rule for rc_define: 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.

What risk level is rc_define? +

rc_define is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rc_define? +

Yes. Add a rate_limit block to the rc_define 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.

How do I block rc_define completely? +

Set action: deny in the PolicyLayer policy for rc_define. 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.

What MCP server provides rc_define? +

rc_define 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.