AI agents use create_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 |
|---|---|---|---|
name | string | Yes | Role name |
is_default_role | boolean | — | Auto-assign this role to new users |
can_manage_links | boolean | — | Can manage tracking links |
can_manage_media | boolean | — | Can manage creatives and media groups |
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 |
can_manage_contracts | boolean | — | Can manage contracts |
Parameters from the server's own tool schema.
This tool creates new roles (a reversible operation), which modifies the system's access control configuration. While not deleting or executing arbitrary code, creating roles with permission settings can expand access and affect system security posture if misused by an AI agent (e.g., creating overly permissive roles).
From the tool's definition Tool name 'create_role' and description 'Create a new role with permission settings' indicate this creates a new administrative entity with access control implications.
Risk signalsHigh parameter count (20 properties)
Attacks that exploit this kind of access
Create a new role with permission settings. 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_role accepts 12 parameters: 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, can_manage_contracts. Required: name. 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_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.
create_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 create_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 create_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.
create_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 →