definir_border_radius

Define border-radius por canto em px. Lados omitidos viram 0. Para arredondar tudo igual, passe os 4 com o mesmo valor. Referência: cards 12-16px; botões 8-12px (ou pílula com valor alto).

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/definir-border-radius.md

WHAT IT DOES

What definir_border_radius does on Atomik Dev

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

RISK

Why definir_border_radius is rated Low

Without any rule in front of it, every call an agent makes to definir_border_radius 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 definir_border_radius 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 definir_border_radius, this is the rule to start with:

definir_border_radius Rate-limited

definir_border_radius 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": {
    "definir_border_radius": {
      "limits": [
        {
          "counter": "definir_border_radius_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 definir_border_radius call is checked against it from then on.

FAQ

Questions about definir_border_radius

What does the definir_border_radius tool do? +

Define border-radius por canto em px. Lados omitidos viram 0. Para arredondar tudo igual, passe os 4 com o mesmo valor. Referência: cards 12-16px; botões 8-12px (ou pílula com valor alto). 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 definir_border_radius? +

Register the Atomik Dev MCP server in PolicyLayer and add a rule for definir_border_radius: 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 definir_border_radius? +

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

Can I rate-limit definir_border_radius? +

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

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

definir_border_radius 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 →