AI agents use create_user to create or update resources in AdButler — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AdButler environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
user_id | string | — | User ID |
attributes | object | — | User attribute values |
user_db_id | number | Yes | User database ID |
Parameters from the server's own tool schema.
This tool creates a new record in the user database with side effects, making it a Write operation. The severity is medium because creating unauthorized or fraudulent user accounts could lead to unauthorized access to AdButler's ad management platform, potentially affecting campaigns and billing downstream, but the action is reversible (unlike Destructive operations).
From the tool's definition create_user description states 'Create a new user in a user database' — the verb 'create' indicates the tool generates a new record that is reversible (user accounts can be disabled, deleted, or modified by other operations).
Attacks that exploit this kind of access
Create a new user in a user database. It is categorised as a Write tool in the AdButler MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_user accepts 3 parameters: user_id, attributes, user_db_id. Required: user_db_id. The full parameter table on this page comes from the server's own tool schema.
Register the AdButler MCP server in PolicyLayer and add a rule for create_user: 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 AdButler. Nothing to install.
create_user 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 create_user 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 create_user. 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.
create_user is provided by the AdButler MCP server (adbutler/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 →