AI agents call color_info to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
color | string | Yes | |
format | string | — |
Parameters from the server's own tool schema.
This tool queries and returns color metadata. It performs no modifications, deletions, code execution, or financial operations. The blast radius of misuse is negligible—an agent cannot cause harm by requesting color information repeatedly or with arbitrary inputs.
From the tool's definition Tool description states 'Get information about a color' — a retrieval operation with no side effects. Returns computed properties like name and complementary color based on input.
Attacks that exploit this kind of access
Get information about a color (name, complementary, etc.). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
color_info accepts 2 parameters: color, format. Required: 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_info: 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_info 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_info 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_info. 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_info 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 →