color_convert

Color Converter (HEX / RGB / HSL) — Convert a color between HEX, RGB and HSL representations.

SERVERGateway SOURCEhttps://wingmanprotocol.com/mcp

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-wingmanprotocol-agent-gateway/color-convert.md

WHAT IT DOES

What color_convert does on Gateway

AI agents call color_convert to retrieve information from Gateway 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
`b`	integer	—	Blue 0-255
`g`	integer	—	Green 0-255
`r`	integer	—	Red 0-255
`hex`	string	—	Hex color, e.g. '#3498db' (or provide r/g/b)

Parameters from the server's own tool schema.

RISK

Why color_convert is rated Low

This tool performs a pure mathematical/format conversion between color representations. It has no side effects, does not read from or write to any external systems, and cannot cause any harm. It is a stateless transformation utility.

From the tool's definition Convert a color between HEX, RGB and HSL representations

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs color_convert safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, 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 Allowed

color_convert is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "color_convert": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every color_convert call is checked against it from then on.

FAQ

Questions about color_convert

What does the color_convert tool do? +

Color Converter (HEX / RGB / HSL) — Convert a color between HEX, RGB and HSL representations. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.

What parameters does color_convert accept? +

color_convert accepts 4 parameters: b, g, r, hex. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on color_convert? +

Register the Gateway 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 Gateway. Nothing to install.

What risk level is color_convert? +

color_convert is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit color_convert? +

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.

How do I block color_convert completely? +

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.

What MCP server provides color_convert? +

color_convert is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gateway, and thousands of servers like it.

This server

All 271 Gateway tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →