wcag_contrast_checker
Compute the WCAG 2.x contrast ratio between two hex colors and whether it passes AA/AAA for normal and large text. Runs on smart-tools.xyz.
This record as markdown: /tools/io-github-9thshini-smart-tools/wcag-contrast-checker.md
What wcag_contrast_checker does on SmartTools
AI agents invoke wcag_contrast_checker to trigger actions in SmartTools. 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 |
|---|---|---|---|
locale | string | — | Language for the source_url link (default en) |
background | string | Yes | Background colour as hex, e.g. #ffffff |
foreground | string | Yes | Text colour as hex, e.g. #767676 |
Parameters from the server's own tool schema.
Why wcag_contrast_checker is rated High
wcag_contrast_checker triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs wcag_contrast_checker safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartTools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wcag_contrast_checker, this is the rule to start with:
wcag_contrast_checker 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 SmartTools, apply this rule, and every wcag_contrast_checker call is checked against it from then on.
Questions about wcag_contrast_checker
Compute the WCAG 2.x contrast ratio between two hex colors and whether it passes AA/AAA for normal and large text. Runs on smart-tools.xyz. It is categorised as a Execute tool in the SmartTools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
wcag_contrast_checker accepts 3 parameters: locale, background, foreground. Required: background, foreground. The full parameter table on this page comes from the server's own tool schema.
Register the SmartTools MCP server in PolicyLayer and add a rule for wcag_contrast_checker: 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 SmartTools. Nothing to install.
wcag_contrast_checker 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 wcag_contrast_checker 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 wcag_contrast_checker. 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.
wcag_contrast_checker is provided by the SmartTools MCP server (https://smart-tools.xyz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartTools, and thousands of servers like it.
Across the catalogue