drupal_update_node · Drupal MCP: Risk & Policy

WHAT IT DOES

What drupal_update_node does on Drupal

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

WHY IT NEEDS A POLICY

Why drupal_update_node needs a policy

This tool modifies existing content reversibly (updates/patches rather than deletes). It does not execute arbitrary code, delete data irreversibly, or move money. However, the severity is elevated to 'high' because unauthorized modification of Drupal nodes could impact published content, user data, or site functionality, and an AI agent with this capability could make unintended changes at scale across a production…

From the tool's definition Tool description states 'Patch an existing node' and 'Pass only the attributes / relationships you want to change', indicating reversible modification of data. The server enables 'CRUD operations on nodes' including updates.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drupal_update_node Rate-limited

drupal_update_node 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": {
    "drupal_update_node": {
      "limits": [
        {
          "counter": "drupal_update_node_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 Drupal, so you can run agents against it safely.

FAQ

Questions about drupal_update_node

What does the drupal_update_node tool do? +

Patch an existing node by UUID. Pass only the attributes / relationships you want to change. It is categorised as a Write tool in the Drupal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on drupal_update_node? +

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

What risk level is drupal_update_node? +

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

Can I rate-limit drupal_update_node? +

Yes. Add a rate_limit block to the drupal_update_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.

How do I block drupal_update_node completely? +

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

What MCP server provides drupal_update_node? +

drupal_update_node is provided by the Drupal MCP server (lucaspretti/drupal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.