element_move · Voog MCP: Risk & Policy

WHAT IT DOES

What element_move does on Voog

AI agents use element_move to create or update resources in Voog — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Voog environment.

WHY IT NEEDS A POLICY

Why element_move needs a policy

Moving/re-ordering elements modifies page structure reversibly—the original content remains intact and the change can be undone. This is a Write operation rather than Destructive (no deletion) or Execute (no code execution).

From the tool's definition Tool name 'element_move' and description 'Re-order or re-parent an element instance' indicates modifying the structure and hierarchy of page elements. This changes the DOM/content structure of the CMS but does not delete data or execute arbitrary code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

element_move Rate-limited

element_move stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "element_move": {
      "limits": [
        {
          "counter": "element_move_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Voog, so you can run agents against it safely.

FAQ

Questions about element_move

What does the element_move tool do? +

Re-order or re-parent an element instance. It is categorised as a Write tool in the Voog MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on element_move? +

Register the Voog MCP server in PolicyLayer and add a rule for element_move: 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 Voog. Nothing to install.

What risk level is element_move? +

element_move is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit element_move? +

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

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

element_move is provided by the Voog MCP server (runnel/voog-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.