create_user_attribute
Create a new user attribute in a user database
This record as markdown: /tools/adbutler/create-user-attribute.md
What create_user_attribute does on AdButler
AI agents use create_user_attribute 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 |
|---|---|---|---|
id | string | — | Field name in the user data (e.g. "signup_datetime") |
type | string | — | Data type of the field |
label | string | — | Descriptive label for the field |
user_db_id | number | Yes | User database ID |
Parameters from the server's own tool schema.
Why create_user_attribute is rated Medium
This tool creates new user attributes in a user database, which is a reversible write operation. It doesn't delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read).
From the tool's definition Tool description states 'Create a new user attribute' - the verb 'create' indicates data creation/modification without deletion. The context of an ad management system managing user attributes suggests reversible data creation.
Attacks that exploit this kind of access
The rule that runs create_user_attribute safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdButler, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_user_attribute, this is the rule to start with:
create_user_attribute 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.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every create_user_attribute call is checked against it from then on.
Questions about create_user_attribute
Create a new user attribute 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_attribute accepts 4 parameters: id, type, label, 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_attribute: 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_attribute 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_attribute 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_attribute. 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_attribute 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.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue