AI agents invoke copypass_run to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
goal | string | — | Optional goal for the copy, such as clarity, conversion, or trust. |
channel | string | — | Optional surface label such as homepage_hero, pricing_section, or onboarding_email. |
profile | string | — | Reserved for later evaluator depth. Defaults to smoke. |
audience | string | — | Optional intended audience for the copy. |
copy_text | string | Yes | The AI-generated copy to review. |
Parameters from the server's own tool schema.
This tool triggers execution of an AI-powered copy generation pipeline. While it doesn't directly delete data (not Destructive), create permanent records in the sense of Write (it's session-scoped), or move money (not Financial), it does initiate and execute a multi-step operation whose output depends on runtime parameters.
From the tool's definition Tool description states it 'Start[s] a scaffold CopyPass run' and 'stores an in-session run record', indicating it initiates an operation that triggers external processing (copy generation scaffolding).
Attacks that exploit this kind of access
Start a scaffold CopyPass run for AI-generated copy. Chunk 1 stores an in-session run record and echoes operator context so later evidence-led copy checks can plug into a stable shape. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
copypass_run accepts 5 parameters: goal, channel, profile, audience, copy_text. Required: copy_text. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for copypass_run: 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 UnClick. Nothing to install.
copypass_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the copypass_run 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 copypass_run. 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.
copypass_run is provided by the UnClick MCP server (@unclick/mcp-server). 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 →