Move a node to a new canvas position.
AI agents use move_node to create or update resources in 247afk Block Editor MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 247afk Block Editor MCP Server environment.
Moving a node modifies the visual layout and state of the editor content reversibly. This is a Write operation—it changes data (node position) but does not delete data or execute external code. The change is reversible: a node can be moved again to restore previous positions. Severity is medium because unintended repositioning could disrupt a user's work, but poses no permanent data loss or external system impact.
From the tool's definition Tool name 'move_node' combined with description 'Move a node to a new canvas position' indicates modification of block editor state.
Attacks that exploit this kind of access
Move a node to a new canvas position. It is categorised as a Write tool in the 247afk Block Editor MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 247afk Block Editor MCP Server MCP server in PolicyLayer and add a rule for move_node: 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 247afk Block Editor MCP Server. Nothing to install.
move_node is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the move_node 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 move_node. 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.
move_node is provided by the 247afk Block Editor MCP Server MCP server (itzdaimy/247afk-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →