update_user_attribute · AdButler MCP: Risk & Policy

WHAT IT DOES

What update_user_attribute does on AdButler

AI agents use update_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.

PARAMETERS

Parameter	Type	Required	Description
`id`	number	Yes	User attribute ID
`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 IT NEEDS A POLICY

Why update_user_attribute needs a policy

This tool modifies existing user attributes in a database, which is a reversible write operation. It does not retrieve data (Read), execute arbitrary code (Execute), permanently delete data (Destructive), or move money (Financial).

From the tool's definition Tool name 'update_user_attribute' and description 'Update an existing user attribute in a user database' directly indicate modification of data. The verb 'update' and context of modifying user database records confirms write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_user_attribute Rate-limited

update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_user_attribute": {
      "limits": [
        {
          "counter": "update_user_attribute_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 AdButler, so you can run agents against it safely.

FAQ

Questions about update_user_attribute

What does the update_user_attribute tool do? +

Update an existing 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.

What parameters does update_user_attribute accept? +

update_user_attribute accepts 4 parameters: id, type, label, user_db_id. Required: id, user_db_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_user_attribute? +

Register the AdButler MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_user_attribute? +

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

Can I rate-limit update_user_attribute? +

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

How do I block update_user_attribute completely? +

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

What MCP server provides update_user_attribute? +

update_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.