list_service_accounts
Manage non-human identities whose API tokens call the DoiT API with a fixed set of permissions. Returns every service account owned by the authenticated customer in a single unpaginated items array, in no guaranteed order. Requires the serviceAccountViewer permission.
This record as markdown: /tools/doit/list-service-accounts.md
What list_service_accounts does on Doit
AI agents call list_service_accounts to retrieve information from Doit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
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.
Why list_service_accounts is rated Low
Even though list_service_accounts only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs list_service_accounts 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 list_service_accounts, this is the rule to start with:
list_service_accounts is read-only, so it stays allowed. 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 list_service_accounts call is checked against it from then on.
Questions about list_service_accounts
Manage non-human identities whose API tokens call the DoiT API with a fixed set of permissions. Returns every service account owned by the authenticated customer in a single unpaginated items array, in no guaranteed order. Requires the serviceAccountViewer permission. It is categorised as a Read tool in the Doit MCP Server, which means it retrieves data without modifying state.
list_service_accounts accepts 1 parameter: customerContext. 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 list_service_accounts: 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.
list_service_accounts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_service_accounts 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 list_service_accounts. 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.
list_service_accounts 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