This record as markdown: /tools/adbutler/create-manager.md
What create_manager does on AdButler
AI agents use create_manager 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 | Manager name |
email | string | Yes | Manager email address |
notes | string | — | Notes about the manager |
password | string | — | Login password (min 8 chars with upper, lower, number). Random if blank. |
position | string | — | Manager position in organization |
is_enabled | boolean | — | Whether the manager account is enabled |
can_manage_links | boolean | — | Can create/edit/delete active tracking links |
can_manage_media | boolean | — | Can manage creatives and media groups |
can_manage_users | boolean | — | Can manage user accounts and permissions |
publisher_access | string | — | Publisher access level |
statistics_access | string | — | Statistics access level |
can_manage_bidders | boolean | — | Can manage bidders |
Parameters from the server's own tool schema.
Why create_manager is rated Medium
This tool creates a new manager account/entity, which is a reversible write operation. It modifies system state by adding a new user or manager record but does not delete data, execute arbitrary code, or move money.
From the tool's definition Tool name 'create_manager' and description 'Create a new manager' indicate creation of a new entity in the AdButler system.
Risk signalsHandles credentials or secrets (password) · High parameter count (24 properties)
Attacks that exploit this kind of access
The rule that runs create_manager 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_manager, this is the rule to start with:
create_manager 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_manager call is checked against it from then on.
Questions about create_manager
Create a new manager. 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_manager accepts 12 parameters: name, email, notes, password, position, is_enabled, can_manage_links, can_manage_media, can_manage_users, publisher_access, statistics_access, can_manage_bidders. Required: name, email. 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_manager: 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_manager 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_manager 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_manager. 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_manager 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