update_customer_group
Manage explicit, named groups of downstream customers and the users scoped to them. Updates the name, customer membership, or both for a customer group owned by the authenticated tenant. Requires the UsersManager permission.
This record as markdown: /tools/doit/update-customer-group.md
What update_customer_group does on Doit
AI agents use update_customer_group to create or update resources in Doit, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Doit environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | |
X-Tenant-Id | string | — | |
customerContext | string | — | Scope the request to a specific customer by ID. Required for DoiT employees (whose token isn't tied to a single customer); omit for direct customer users. |
customerGroupId | string | Yes | |
memberCustomerIds | array | — |
Parameters from the server's own tool schema.
Why update_customer_group is rated Medium
An AI agent can call update_customer_group faster than any human can review: one bad instruction and it creates or modifies resources in Doit by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs update_customer_group safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Doit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_customer_group, this is the rule to start with:
update_customer_group 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 Doit, apply this rule, and every update_customer_group call is checked against it from then on.
Questions about update_customer_group
Manage explicit, named groups of downstream customers and the users scoped to them. Updates the name, customer membership, or both for a customer group owned by the authenticated tenant. Requires the UsersManager permission. It is categorised as a Write tool in the Doit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_customer_group accepts 5 parameters: name, X-Tenant-Id, customerContext, customerGroupId, memberCustomerIds. Required: customerGroupId. The full parameter table on this page comes from the server's own tool schema.
Register the Doit MCP server in PolicyLayer and add a rule for update_customer_group: 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 Doit. Nothing to install.
update_customer_group 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_customer_group 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_customer_group. 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_customer_group is provided by the Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Doit, and thousands of servers like it.
This server
Across the catalogue