generate_color_scheme
Generates a Material Design color scheme from one or more key colors. Always use this when you need to create a color scheme for an application. The input is one or more named colors in hex format, and the output is a color scheme with a map of color role names to colors in hex format.
This record as markdown: /tools/com-googleapis-design-mcp/generate-color-scheme.md
What generate_color_scheme does on Mcp
AI agents invoke generate_color_scheme to trigger actions in Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
primaryKey | string | Yes | Required. The primary key color used as the main seed for the scheme. Can be a 6-character hex code (e.g., "#4285F4" or "4285F4"), or any standard CSS color nam |
tertiaryKey | string | — | Optional. The tertiary key color used to generate the color scheme. If omitted, it will be automatically derived from the other keys. Can be a hex code or any C |
secondaryKey | string | — | Optional. The secondary key color used to generate the color scheme. If omitted, it will be automatically derived from the other keys. Can be a hex code or any |
backgroundKey | string | — | Optional. The neutral key color used to generate the color scheme. If omitted, it will be automatically derived from the other keys. Can be a hex code or any CS |
contrastLevel | number | — | Optional. The contrast level of the color scheme. Values range from -1 (minimum contrast) to 1 (maximum contrast). 0 represents standard contrast (i.e. the desi |
optionalTheme | string | — | Optional. Whether to generate a light or dark theme. If unspecified, and a background key is supplied, it will be inferred from that. If not, it will default to |
optionalSchemeVariant | string | — | Optional. If only the primary key color is supplied, this will select which variant of the color scheme to use. If only the primary key color is supplied and th |
Parameters from the server's own tool schema.
Why generate_color_scheme is rated High
The tool performs a computation/generation operation (algorithmic color scheme generation) rather than retrieving stored data. It transforms input hex colors into a full Material Design color scheme. While it has no persistent side effects and is read-like in some respects, it executes a generative process. Severity is low because misuse only produces color values with no system impact.
From the tool's definition 'Generates a Material Design color scheme from one or more key colors' — this tool actively computes/generates output from inputs rather than simply reading existing data
Attacks that exploit this kind of access
The rule that runs generate_color_scheme safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_color_scheme, this is the rule to start with:
generate_color_scheme stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every generate_color_scheme call is checked against it from then on.
Questions about generate_color_scheme
Generates a Material Design color scheme from one or more key colors. Always use this when you need to create a color scheme for an application. The input is one or more named colors in hex format, and the output is a color scheme with a map of color role names to colors in hex format. It is categorised as a Execute tool in the Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
generate_color_scheme accepts 7 parameters: primaryKey, tertiaryKey, secondaryKey, backgroundKey, contrastLevel, optionalTheme, optionalSchemeVariant. Required: primaryKey. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for generate_color_scheme: 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 Mcp. Nothing to install.
generate_color_scheme is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the generate_color_scheme 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 generate_color_scheme. 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.
generate_color_scheme is provided by the MCP server (https://design.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue