Medium Risk

ui_states

Generate a complete WCAG-compliant UI state palette from a brand hex. Returns colours for: brand, hover, active, disabled, focus ring, success, warning, error, info, surface subtle, surface strong. All states computed for contrast against your background colour. Returns hex, contrast ratio, WCAG ...

Part of the Colour Memory server.

ui_states can modify Colour Memory data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE COLOUR MEMORY →

Free to start. No card required.

AI agents use ui_states to create or modify resources in Colour Memory. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call ui_states repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Colour Memory.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ui_states": {
      "limits": [
        {
          "counter": "ui_states_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Colour Memory policy for all 65 tools.

Get this rule live on your own Colour Memory server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY COLOUR MEMORY →

View all 65 tools →

These attack patterns abuse exactly the kind of access ui_states gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so ui_states only ever does what you allow.

SECURE COLOUR MEMORY →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the ui_states tool do? +

Generate a complete WCAG-compliant UI state palette from a brand hex. Returns colours for: brand, hover, active, disabled, focus ring, success, warning, error, info, surface subtle, surface strong. All states computed for contrast against your background colour. Returns hex, contrast ratio, WCAG grade, and usage note for each state. Includes CSS custom properties ready to paste. Supports light and dark mode. Use before building any UI component system.. It is categorised as a Write tool in the Colour Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ui_states? +

Register the Colour Memory MCP server in PolicyLayer and add a rule for ui_states: 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 Colour Memory. Nothing to install.

What risk level is ui_states? +

ui_states is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ui_states? +

Yes. Add a rate_limit block to the ui_states 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 ui_states completely? +

Set action: deny in the PolicyLayer policy for ui_states. 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 ui_states? +

ui_states is provided by the Colour Memory MCP server (https://colour-memory-api-production.up.railway.app/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Colour Memory tool call.

Deterministic rules across all 65 Colour Memory tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.