This record as markdown: /tools/creativelead-unclick/color-mix.md
What color_mix does on UnClick
AI agents call color_mix to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
ratio | number | — | |
color1 | string | — | |
color2 | string | — |
Parameters from the server's own tool schema.
Why color_mix is rated Low
This is a pure utility function that performs a mathematical/visual calculation on color values. It retrieves or computes a result based on inputs with no side effects, data modifications, or external system impacts. The trivial nature of the operation and its isolated scope classify it as a low-risk read operation.
From the tool's definition Tool name 'color_mix' and description 'Mix two colors together' indicates a computational operation that takes input colors and returns a result without modifying any persistent state, creating data, executing external operations, or causing side effects.
Attacks that exploit this kind of access
The rule that runs color_mix safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For color_mix, this is the rule to start with:
color_mix is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every color_mix call is checked against it from then on.
Questions about color_mix
Mix two colors together. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
color_mix accepts 3 parameters: ratio, color1, color2. 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 color_mix: 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.
color_mix is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the color_mix 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 color_mix. 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.
color_mix is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue