ux_design

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

Category Write

Risk class Medium

Parameters 00 required

WHAT IT DOES

What ux_design does on RC Engine

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

The ux_design tool creates new design deliverables (HTML wireframes, design specs) and writes them to the filesystem. This is a reversible Write operation - designs can be deleted or replaced without permanent loss of core data. It does not execute arbitrary code, delete data irreversibly, or have financial impact.

From the tool's definition Tool "produces" design options and "saves to rc-method/design/" - creates new design artifacts and files

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ux_design Rate-limited

ux_design 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": {
    "ux_design": {
      "limits": [
        {
          "counter": "ux_design_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 ux_design

What does the ux_design tool do? +

Generate visual design options with HTML wireframes. Call after PRD is created (Phase 2+). Produces 1 or 3 design options based on ICP, competitor gaps, and design trends. Each option includes a design spec (colors, typography, layout) and self-contained HTML wireframes (lo-fi + hi-fi). Saves to rc-method/design/. Pass option_count=1 for budget-conscious, option_count=3 for full comparison. 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 ux_design? +

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

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

Can I rate-limit ux_design? +

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

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

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