color_convert
Convert a color between HEX, RGB, HSL, and other formats.
This record as markdown: /tools/creativelead-unclick/color-convert.md
What color_convert does on UnClick
AI agents call color_convert as a supporting operation in UnClick workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | — | |
from | string | — | |
color | string | — |
Parameters from the server's own tool schema.
Why color_convert is rated Low
This tool performs a pure local computation — converting color values between formats. It has no side effects, does not read from or write to any external system, does not execute code, and carries no financial or destructive implications. It is a stateless transformation utility.
From the tool's definition Convert a color between HEX, RGB, HSL, and other formats.
Attacks that exploit this kind of access
The rule that runs color_convert 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_convert, this is the rule to start with:
color_convert gets a rate cap, and 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_convert call is checked against it from then on.
Questions about color_convert
Convert a color between HEX, RGB, HSL, and other formats. It is categorised as a Other tool in the UnClick MCP Server, which means it performs auxiliary operations.
color_convert accepts 3 parameters: to, from, color. 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_convert: 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_convert is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the color_convert 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_convert. 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_convert 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