AI agents use update_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 |
|---|---|---|---|
id | number | Yes | Manager ID |
name | string | — | Manager name |
email | string | — | Manager email address |
notes | string | — | Notes about the manager |
password | string | — | Login password |
position | string | — | Manager position |
is_enabled | boolean | — | Whether the manager account is enabled |
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 |
Parameters from the server's own tool schema.
This tool modifies manager data (likely user/admin records within AdButler) but does not permanently delete, execute external operations, or move money. While update operations carry risk (incorrect modifications could impact system administration), they are reversible and typical Write operations. Severity is medium given the administrative nature of manager records and potential impact on system access control.
From the tool's definition Tool name 'update_manager' and description 'Update an existing manager' indicate modification of an existing manager entity. The 'update' action is reversible and does not delete or destroy data.
Risk signalsHandles credentials or secrets (password) · High parameter count (25 properties)
Attacks that exploit this kind of access
Update an existing 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.
update_manager accepts 12 parameters: id, name, email, notes, password, position, is_enabled, can_manage_links, can_manage_media, can_manage_users, publisher_access, statistics_access. 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_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.
update_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 update_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 update_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.
update_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.
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 →