mover_elemento
Move um elemento para dentro de outro container, em uma posição específica. ATENÇÃO: $e.run move é implementado como delete+create; refs ao ID antigo ficam stale.
This record as markdown: /tools/atomik-dev-mcp/mover-elemento.md
What mover_elemento does on Atomik Dev
AI agents call mover_elemento to permanently remove resources in Atomik Dev, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why mover_elemento is rated Critical
An AI agent that decides to call mover_elemento doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Atomik Dev is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs mover_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 mover_elemento, this is the rule to start with:
mover_elemento is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Atomik Dev, apply this rule, and every mover_elemento call is checked against it from then on.
Questions about mover_elemento
Move um elemento para dentro de outro container, em uma posição específica. ATENÇÃO: $e.run move é implementado como delete+create; refs ao ID antigo ficam stale. It is categorised as a Destructive tool in the Atomik Dev MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Atomik Dev MCP server in PolicyLayer and add a rule for mover_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.
mover_elemento is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the mover_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.
Set action: deny in the PolicyLayer policy for mover_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.
mover_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