create_ticket_comment
Adds a comment to an existing support ticket. For customers, comments are always public. For DoiT employees, comments can be marked as private (internal notes) by setting the private field to true.
This record as markdown: /tools/doit/create-ticket-comment.md
What create_ticket_comment does on Doit
AI agents use create_ticket_comment 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 |
|---|---|---|---|
body | string | Yes | The text content of the comment (required, must be non-empty). |
private | boolean | — | If true, creates a private internal note. Only honored for DoiT employees; ignored for customers. |
ticketId | string | Yes | The numeric ID of the support ticket to add a comment to. |
Parameters from the server's own tool schema.
Why create_ticket_comment is rated Medium
An AI agent can call create_ticket_comment 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.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs create_ticket_comment 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_ticket_comment, this is the rule to start with:
create_ticket_comment 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_ticket_comment call is checked against it from then on.
Questions about create_ticket_comment
Adds a comment to an existing support ticket. For customers, comments are always public. For DoiT employees, comments can be marked as private (internal notes) by setting the private field to true. 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_ticket_comment accepts 3 parameters: body, private, ticketId. Required: body, 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 create_ticket_comment: 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_ticket_comment 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_ticket_comment 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_ticket_comment. 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_ticket_comment 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