AI agents call drupal_list_users to retrieve information from Drupal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user information from a Drupal site without creating, modifying, or deleting any data. It is a straightforward read operation that presents minimal risk of unintended consequences when invoked by an AI agent, assuming the configured account has appropriate permissions. The blast radius is limited to potential information disclosure of user lists.
From the tool's definition Tool name 'drupal_list_users' and description 'List Drupal users' indicate a retrieval operation with no side effects. The permission requirement ('view users') confirms read-only access.
Attacks that exploit this kind of access
List Drupal users. Requires the configured account to have permission to view users. It is categorised as a Read tool in the Drupal MCP Server, which means it retrieves data without modifying state.
Register the Drupal MCP server in PolicyLayer and add a rule for drupal_list_users: 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_list_users is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the drupal_list_users 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_list_users. 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_list_users 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 →