Generate a Design Research Brief during Phase 2 (Define). Analyzes ICP, competitors, and brand constraints to produce research-backed design direction. Output: ICP design profile, competitive design landscape, emotional design strategy, information architecture, cognitive design principles, trend...
AI agents use design_research_brief 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 a design research document by analyzing inputs and writing structured outputs to a markdown file. It is a Write operation because it creates new data artifacts without deleting or executing external commands. The severity is low because the output is informational design guidance with no destructive effects, no code execution, and no financial implications.
From the tool's definition Tool produces and saves outputs to a file (rc-method/design/DESIGN-RESEARCH-BRIEF.md), which constitutes creating/modifying data. The description indicates it 'generates' a research brief and 'saves' it, characteristic Write operations.
Attacks that exploit this kind of access
Generate a Design Research Brief during Phase 2 (Define). Analyzes ICP, competitors, and brand constraints to produce research-backed design direction. Output: ICP design profile, competitive design landscape, emotional design strategy, information architecture, cognitive design principles, trend recommendations, and design constraints. Saves to rc-method/design/DESIGN-RESEARCH-BRIEF.md. Call AFTER prd is created. 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 design_research_brief: 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.
design_research_brief 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 design_research_brief 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 design_research_brief. 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.
design_research_brief 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 →