rc_sequence

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

Category Write

Risk class Medium

Parameters 00 required

WHAT IT DOES

What rc_sequence does on RC Engine

AI agents use rc_sequence 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_sequence needs a policy

The tool reads existing PRD artifacts and writes new structured task files to the filesystem (rc-method/tasks/). It creates new data artifacts but does not delete, execute code, or involve financial transactions. The action is reversible (files can be deleted or overwritten), placing it firmly in the Write category.

From the tool's definition Auto-generates a sequenced, dependency-ordered task list from the approved PRD and architecture... Saved to rc-method/tasks/

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rc_sequence Rate-limited

rc_sequence 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_sequence": {
      "limits": [
        {
          "counter": "rc_sequence_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_sequence

What does the rc_sequence tool do? +

Phase 4 (Sequence). Auto-generates a sequenced, dependency-ordered task list from the approved PRD and architecture. Each task gets an ID (TASK-001, TASK-002...) with estimated effort and dependencies. Saved to rc-method/tasks/. No user input needed - reads PRD artifacts automatically. Present the task list to user for approval. Prerequisites: Phase 3 gate approved. After gate approval: moves to Phase 5 (Validate). 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_sequence? +

Register the RC Engine MCP server in PolicyLayer and add a rule for rc_sequence: 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_sequence? +

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

Can I rate-limit rc_sequence? +

Yes. Add a rate_limit block to the rc_sequence 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_sequence completely? +

Set action: deny in the PolicyLayer policy for rc_sequence. 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_sequence? +

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