checar_design

SERVERAtomik Dev SOURCE@atomik-dev/mcp

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/atomik-dev-mcp/checar-design.md

WHAT IT DOES

What checar_design does on Atomik Dev

AI agents call checar_design as a supporting operation in Atomik Dev workflows.

RISK

Why checar_design is rated Low

Without any rule in front of it, every call an agent makes to checar_design happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs checar_design safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Atomik Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For checar_design, this is the rule to start with:

checar_design Rate-limited

checar_design gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "checar_design": {
      "limits": [
        {
          "counter": "checar_design_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about checar_design

What does the checar_design tool do? +

Roda um detector determinístico de qualidade de design sobre o RENDER real do preview (estilos computados, não o JSON declarado). Regras: corpo-pequeno (<16px), contraste-wcag (4.5:1 corpo / 3:1 texto grande; fundos com imagem contam como indeterminados), glow-cromatico, borda-colorida-grossa, fonte-banida, roxo-ia, touch-target (só no mobile), gradient-text, espacamento-monotono, cinza-sobre-cromatico. Rode ao final de cada seção e corrija os erros antes de prosseguir. It is categorised as a Other tool in the Atomik Dev MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on checar_design? +

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

What risk level is checar_design? +

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

Can I rate-limit checar_design? +

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

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

checar_design is provided by the Atomik Dev MCP server (@atomik-dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Atomik Dev, and thousands of servers like it.

This server

All 64 Atomik Dev tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →