AI agents use update_role 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 | number | Yes | Role ID |
name | string | — | Role name |
is_default_role | boolean | — | Auto-assign to new users |
can_manage_links | boolean | — | Can manage tracking links |
can_manage_media | boolean | — | Can manage creatives |
can_manage_users | boolean | — | Can manage users |
publisher_access | string | — | Publisher access level |
statistics_access | string | — | Statistics access level |
can_manage_bidders | boolean | — | Can manage bidders |
can_manage_billing | boolean | — | Can manage billing |
can_manage_targets | boolean | — | Can manage targets |
can_manage_tickets | boolean | — | Can manage tickets |
Parameters from the server's own tool schema.
This tool modifies an existing role, which is a reversible write operation affecting authorization and access control. The high severity reflects that role misconfiguration could grant unintended permissions to multiple users and impact system security, though the operation remains reversible (can be undone via another update).
From the tool's definition Tool name 'update_role' with description 'Update an existing role' indicates modification of access control configuration. Sibling tools show patterns of archive/update operations on business entities (advertisers, campaigns, publishers, zones).
Risk signalsHigh parameter count (21 properties)
Attacks that exploit this kind of access
Update an existing role. 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.
update_role accepts 12 parameters: id, name, is_default_role, can_manage_links, can_manage_media, can_manage_users, publisher_access, statistics_access, can_manage_bidders, can_manage_billing, can_manage_targets, can_manage_tickets. Required: 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 update_role: 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.
update_role 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 update_role 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 update_role. 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.
update_role 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 →