remove_ticket_tags
Create and manage support tickets with DoiT. Removes one or more tags from an existing support request. The operation is surgical — only the tags listed in the request are removed; tags not listed are preserved. Removing a tag that is not present is a successful no-op. For customers, the system a...
This record as markdown: /tools/doit/remove-ticket-tags.md
What remove_ticket_tags does on Doit
AI agents call remove_ticket_tags to permanently remove resources in Doit, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
tags | array | Yes | List of tags to add or remove. Customer-submitted tags are auto-prefixed with `customer_tag/`. |
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 remove_ticket_tags is rated Critical
An AI agent that decides to call remove_ticket_tags doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Doit is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs remove_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 remove_ticket_tags, this is the rule to start with:
remove_ticket_tags is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Doit, apply this rule, and every remove_ticket_tags call is checked against it from then on.
Questions about remove_ticket_tags
Create and manage support tickets with DoiT. Removes one or more tags from an existing support request. The operation is surgical — only the tags listed in the request are removed; tags not listed are preserved. Removing a tag that is not present is a successful no-op. For customers, the system applies the same customer_tag/ namespace mapping as on add, so a customer who added my_tag (stored as customer_tag/my_tag) can remove it by sending my_tag. It is categorised as a Destructive tool in the Doit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_ticket_tags accepts 3 parameters: tags, ticketId, customerContext. Required: tags, 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 remove_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.
remove_ticket_tags is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_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.
Across the catalogue