AI agents use drupal_create_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.
This tool creates new content (nodes) in a Drupal site, which is a reversible modification. It does not delete or destroy data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). Write is the appropriate category. Severity is medium because creating nodes could introduce spam, malicious content, or data pollution, but the effects are reversible via drupal_delete_node.
From the tool's definition Tool description states 'Create a new node' with attributes and relationships. The server description confirms 'CRUD operations on nodes' where Create is a write operation.
Attacks that exploit this kind of access
Create a new node. Pass attributes (and optional relationships) using JSON:API field names. 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.
Register the Drupal MCP server in PolicyLayer and add a rule for drupal_create_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.
drupal_create_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 drupal_create_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 drupal_create_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.
drupal_create_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.
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 →