This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/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 | Yes | |
color2 | string | Yes |
Parameters from the server's own tool schema.
Why color_mix is rated Low
This tool performs a stateless color blending calculation with no side effects on any system, database, or external service. It is a read-like operation in the sense that it retrieves a computed result based on inputs without altering any state. The minimal blast radius and lack of any destructive, executable, or financial capability warrant a 'low' severity classification.
From the tool's definition Tool name 'color_mix' and description 'Mix two colors together' indicate a pure computational operation that takes two color inputs and returns a blended result. No data creation, modification, deletion, code execution, or financial transactions are involved.
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. Required: 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 (@unclick/mcp-server). 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