node_update · Voog MCP: Risk & Policy

WHAT IT DOES

What node_update does on Voog

AI agents use node_update 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 node_update needs a policy

This tool creates or modifies data reversibly, fitting the Write category. It operates on a CMS where nodes are content entities that can be updated. Severity is medium because unauthorized updates to CMS nodes could alter website content, but the change is not destructive and can typically be reverted. Confidence is high based on clear indication of an update/modification operation in a CMS context.

From the tool's definition Tool name 'node_update' and description 'Update a node' indicate modification of existing data. In the context of a CMS (Voog), nodes represent content structures. The action is reversible and does not delete data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

node_update Rate-limited

node_update 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": {
    "node_update": {
      "limits": [
        {
          "counter": "node_update_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 node_update

What does the node_update tool do? +

Update a node. 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 node_update? +

Register the Voog MCP server in PolicyLayer and add a rule for node_update: 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 node_update? +

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

Can I rate-limit node_update? +

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

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

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