criar_elemento

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/criar-elemento.md

WHAT IT DOES

What criar_elemento does on Atomik Dev

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

RISK

Why criar_elemento is rated Low

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

criar_elemento Rate-limited

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

FAQ

Questions about criar_elemento

What does the criar_elemento tool do? +

Cria um elemento arbitrário (container ou widget V4) dentro de um pai específico. O model segue o schema V4 (elType, widgetType, settings, styles, elements — todo nó precisa de elements: [], mesmo widgets folha). Os IDs enviados são REMAPEADOS: use os IDs retornados na resposta, nunca os que você enviou. Consulte guia_design(secao:. 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 criar_elemento? +

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

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

Can I rate-limit criar_elemento? +

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

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

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