Update input field values on an existing node. Only the fields you provide are changed — other data is preserved. Use get_graph first to get the node id.
AI agents use update_node_data 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.
update_node_data modifies existing node state within a block editor graph by changing input field values. This is a reversible Write operation—users can undo changes or revert to previous values. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely read data (Read).
From the tool's definition Tool description states 'Update input field values on an existing node' and 'Only the fields you provide are changed — other data is preserved.' This is a modification operation on existing data.
Attacks that exploit this kind of access
Update input field values on an existing node. Only the fields you provide are changed — other data is preserved. Use get_graph first to get the node id. 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 update_node_data: 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.
update_node_data 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 update_node_data 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 update_node_data. 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.
update_node_data 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 →