update_service_account

SERVERDoit SOURCE@doitintl/doit-mcp-server

Medium RISK CLASS

Category Write

Parameters 83 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/doit/update-service-account.md

WHAT IT DOES

What update_service_account does on Doit

AI agents use update_service_account 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
`id`	string	Yes
`name`	string	—	New name, unique among the customer's service accounts. Leading or trailing whitespace returns `400`.
`dryRun`	boolean	—
`If-Match`	string	Yes
`description`	object	—
`permissions`	object	—
`Idempotency-Key`	string	Yes
`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.

Parameters from the server's own tool schema.

RISK

Why update_service_account is rated Medium

An AI agent can call update_service_account 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.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_service_account 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_service_account, this is the rule to start with:

update_service_account Rate-limited

update_service_account 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_service_account": {
      "limits": [
        {
          "counter": "update_service_account_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Doit, apply this rule, and every update_service_account call is checked against it from then on.

FAQ

Questions about update_service_account

What does the update_service_account tool do? +

Manage non-human identities whose API tokens call the DoiT API with a fixed set of permissions. Partially updates a service account with an application/merge-patch+json body (RFC 7396). Omitted or null fields stay unchanged; an explicit empty string clears description. permissions replaces the whole list, and [] removes every permission. With dryRun=true the request goes through the same checks as a real update (If-Match, name bounds and uniqueness, permission names, caller scope) and returns the service account as it would look after the patch, without changing anything. Requires the serviceAccountManager 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.

What parameters does update_service_account accept? +

update_service_account accepts 8 parameters: id, name, dryRun, If-Match, description, permissions, Idempotency-Key, customerContext. Required: id, If-Match, Idempotency-Key. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_service_account? +

Register the Doit MCP server in PolicyLayer and add a rule for update_service_account: 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.

What risk level is update_service_account? +

update_service_account is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_service_account? +

Yes. Add a rate_limit block to the update_service_account 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.

How do I block update_service_account completely? +

Set action: deny in the PolicyLayer policy for update_service_account. 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.

What MCP server provides update_service_account? +

update_service_account 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.

KEEP EXPLORING

More on Doit, and thousands of servers like it.

This server

All 238 Doit tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →