New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

medir_elemento

Mede o elemento RENDERIZADO no preview: posição/tamanho reais (getBoundingClientRect) + ~35 estilos computados (fontes, cores, espaçamentos, flex, borda, sombra) + fundo efetivo (herdado) + o filho de texto real. Use para conferir se o resultado visual bate com o pretendido — a medição é do break...

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

What medir_elemento does on Atomik Dev

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

Why medir_elemento is rated Low

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

Questions about medir_elemento

What does the medir_elemento tool do? +

Mede o elemento RENDERIZADO no preview: posição/tamanho reais (getBoundingClientRect) + ~35 estilos computados (fontes, cores, espaçamentos, flex, borda, sombra) + fundo efetivo (herdado) + o filho de texto real. Use para conferir se o resultado visual bate com o pretendido — a medição é do breakpoint ATUAL do editor (use mudar_breakpoint_editor antes para medir tablet/mobile). 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 medir_elemento? +

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

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

Can I rate-limit medir_elemento? +

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

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

medir_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.

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Atomik Dev's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.