create_service_account_token
Manage non-human identities whose API tokens call the DoiT API with a fixed set of permissions. Mints an API token for the service account and returns its accessToken once. The token inherits the service account's permissions as they stand at creation; there is no per-token scoping. Returns 409 w...
This record as markdown: /tools/doit/create-service-account-token.md
What create_service_account_token does on Doit
AI agents use create_service_account_token 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 | Yes | Name, unique among the service account's tokens. Leading or trailing whitespace returns `400`. |
dryRun | boolean | — | |
expiresTime | string | — | When the token should stop authenticating. Omit to let the server set the default expiry. |
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. |
serviceAccountId | string | Yes |
Parameters from the server's own tool schema.
Why create_service_account_token is rated Medium
An AI agent can call create_service_account_token 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 create_service_account_token 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 create_service_account_token, this is the rule to start with:
create_service_account_token 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 create_service_account_token call is checked against it from then on.
Questions about create_service_account_token
Manage non-human identities whose API tokens call the DoiT API with a fixed set of permissions. Mints an API token for the service account and returns its accessToken once. The token inherits the service account's permissions as they stand at creation; there is no per-token scoping. Returns 409 when the service account already has a token of the same name, and 422 at the cap of 10 tokens. dryRun=true checks the name bounds only, then returns a preview without creating anything. It does not verify that the service account exists, that the name is unused, or that the account is under the token cap, so a dry run can succeed where the real create then returns 404, 409 or 422. Requires the serviceAccountCreator 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.
create_service_account_token accepts 6 parameters: name, dryRun, expiresTime, Idempotency-Key, customerContext, serviceAccountId. Required: name, Idempotency-Key, serviceAccountId. 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 create_service_account_token: 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.
create_service_account_token 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_service_account_token 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_service_account_token. 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_service_account_token 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