list_labels
Use this when the user wants to see their DoiT console labels for organizing reports, budgets, alerts, allocations, metrics and annotations. Returns label metadata; these are not cloud resource labels. Do NOT use this for annotations (use list_annotations) or label assignments (use get_label_assi...
This record as markdown: /tools/doit/list-labels.md
What list_labels does on Doit
AI agents call list_labels 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 |
|---|---|---|---|
filter | string | — | Filter using key:value, with different keys joined by | (AND). Repeated keys are rejected (400); values match exactly and case-sensitively. Supported keys: name |
sortBy | string | — | A field by which the results will be sorted. Accepted values: id, name, type, createTime, updateTime. |
pageToken | string | — | Page token, returned by a previous call, to request the next page of results. |
sortOrder | string | — | The sort order for results. Accepted values: asc, desc. |
maxResults | string | — | The maximum number of results per page, as an integer string (1-500). Out-of-range integers fall back to 50; non-integers are rejected. This tool defaults to 50 |
Parameters from the server's own tool schema.
Why list_labels is rated Low
Even though list_labels 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_labels 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_labels, this is the rule to start with:
list_labels 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_labels call is checked against it from then on.
Questions about list_labels
Use this when the user wants to see their DoiT console labels for organizing reports, budgets, alerts, allocations, metrics and annotations. Returns label metadata; these are not cloud resource labels. Do NOT use this for annotations (use list_annotations) or label assignments (use get_label_assignments). It is categorised as a Read tool in the Doit MCP Server, which means it retrieves data without modifying state.
list_labels accepts 5 parameters: filter, sortBy, pageToken, sortOrder, maxResults. 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_labels: 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_labels 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_labels 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_labels. 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_labels 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