Evaluates typography elements against a principled accessibility rubric. COST: $0.05 USDC via x402 on Base-compatible EVM network per call. Goes beyond what axe/Lighthouse/WAVE can check — evaluates design judgment, not just numeric compliance. Catches issues like: - Contrast that passes WCAG 4.5...
Risk signalsHigh parameter count (16 properties)
Part of the Axcess — Design Accessibility Evaluation server.
Free to start. No card required.
AI agents call evaluate_typography to retrieve information from Axcess — Design Accessibility Evaluation without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though evaluate_typography only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"evaluate_typography": {}
}
}See the full Axcess — Design Accessibility Evaluation policy for all 3 tools.
These attack patterns abuse exactly the kind of access evaluate_typography gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Evaluates typography elements against a principled accessibility rubric. COST: $0.05 USDC via x402 on Base-compatible EVM network per call. Goes beyond what axe/Lighthouse/WAVE can check — evaluates design judgment, not just numeric compliance. Catches issues like: - Contrast that passes WCAG 4.5:1 but fails visually due to thin font weight - Body text that meets minimum size requirements but is still too small for comfortable reading - Line heights that technically comply but impede readability for dyslexic users - Extended all-caps or italic text that passes all AA criteria but impairs reading - Text on gradient/image backgrounds where scanner sampling is unreliable - Heading sizes that are technically correct but visually indistinct from body Args: - elements: Array of 1–50 typography element objects with font/color properties - screen_name: Optional label for the evaluation report Each element requires: element_type, font_size, font_weight, line_height, color_hex, background_color_hex. Returns: Structured report with: - Per-element scores (0–100) - Specific issues with severity (critical/major/minor) - WCAG references and what automated tools miss - Concrete fix recommendations - Overall score and verdict (pass/needs_work/fail) - Top issues sorted by severity Example use: Extract text layer properties from Figma using get_design_context, pass the typography properties to this tool for evaluation before shipping.. It is categorised as a Read tool in the Axcess — Design Accessibility Evaluation MCP Server, which means it retrieves data without modifying state.
Register the Axcess — Design Accessibility Evaluation MCP server in PolicyLayer and add a rule for evaluate_typography: 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 Axcess — Design Accessibility Evaluation. Nothing to install.
evaluate_typography 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 evaluate_typography 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 evaluate_typography. 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.
evaluate_typography is provided by the Axcess — Design Accessibility Evaluation MCP server (https://axcess-mcp-server.fly.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Axcess — Design Accessibility Evaluation 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.