ler_elemento

Lê o JSON completo de um elemento existente no editor (settings, styles, widgetType, elementos filhos). Use para inspecionar um nó antes de editar.

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

WHAT IT DOES

What ler_elemento does on Atomik Dev

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

RISK

Why ler_elemento is rated Low

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

ler_elemento Rate-limited

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

FAQ

Questions about ler_elemento

What does the ler_elemento tool do? +

Lê o JSON completo de um elemento existente no editor (settings, styles, widgetType, elementos filhos). Use para inspecionar um nó antes de editar. 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 ler_elemento? +

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

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

Can I rate-limit ler_elemento? +

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

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

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