list_ticket_tags
Create and manage support tickets with DoiT. Returns the tags currently set on a support request. DoiT employee (doer) callers receive the full tag set verbatim, including internal namespaces (e.g. tier/*, synapse_*). Customer callers receive only tags under the customer_tag/ namespace, with that...
This record as markdown: /tools/doit/list-ticket-tags.md
What list_ticket_tags does on Doit
AI agents call list_ticket_tags 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 |
|---|---|---|---|
ticketId | number | 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.
Why list_ticket_tags is rated Low
Even though list_ticket_tags 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_ticket_tags 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_ticket_tags, this is the rule to start with:
list_ticket_tags 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_ticket_tags call is checked against it from then on.
Questions about list_ticket_tags
Create and manage support tickets with DoiT. Returns the tags currently set on a support request. DoiT employee (doer) callers receive the full tag set verbatim, including internal namespaces (e.g. tier/*, synapse_*). Customer callers receive only tags under the customer_tag/ namespace, with that prefix stripped (e.g. a tag added as billing reads back as billing). Always present; empty array when the caller has no visible tags. It is categorised as a Read tool in the Doit MCP Server, which means it retrieves data without modifying state.
list_ticket_tags accepts 2 parameters: ticketId, customerContext. Required: ticketId. 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_ticket_tags: 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_ticket_tags 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_ticket_tags 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_ticket_tags. 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_ticket_tags 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