Generate the full Content Strategy & Copy System: voice/tone, page-level copy with variants, microcopy library, CTA matrix, and SEO content map. Call AFTER copy_research_brief. Requires the screen inventory (list of screen names). Saves to rc-method/copy/COPY-SYSTEM.md.
AI agents use copy_generate 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.
The tool generates and persists copy/content strategy documents (voice, tone, variants, microcopy, CTAs, SEO maps) to a markdown file. This is a Write operation—it creates new content reversibly (the file can be edited or deleted later). It does not execute code, delete data irreversibly, or trigger external financial/destructive actions.
From the tool's definition 'Generate the full Content Strategy & Copy System' and 'Saves to rc-method/copy/COPY-SYSTEM.md' indicate the tool creates and writes structured content artifacts to persistent storage.
Attacks that exploit this kind of access
Generate the full Content Strategy & Copy System: voice/tone, page-level copy with variants, microcopy library, CTA matrix, and SEO content map. Call AFTER copy_research_brief. Requires the screen inventory (list of screen names). Saves to rc-method/copy/COPY-SYSTEM.md. 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 copy_generate: 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.
copy_generate 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 copy_generate 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 copy_generate. 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.
copy_generate 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 →