Add an admin-only internal note to a ticket. Notes are not visible to the client and do not trigger email notifications.
AI agents use whmcs_add_ticket_note to create or update resources in Whmcs — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Whmcs environment.
This tool creates or appends data (an internal note) to an existing ticket record. This is a reversible modification with no side effects beyond the ticket system itself. It does not execute external code, delete data, move money, or trigger notifications. The blast radius is low—a malicious internal note could be misleading but is easily removed or overwritten by an administrator.
From the tool's definition Tool description states it 'Add[s] an admin-only internal note to a ticket', which creates/modifies data (the ticket's internal notes) in a reversible manner. Notes are explicitly non-destructive and do not trigger external notifications.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access whmcs_add_ticket_note gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Whmcs, and nothing reaches the server without passing your rules. This is the rule we recommend for whmcs_add_ticket_note:
{
"version": "1",
"default": "deny",
"tools": {
"whmcs_add_ticket_note": {
"limits": [
{
"counter": "whmcs_add_ticket_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} whmcs_add_ticket_note 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.
Free to start. No card required.
Add an admin-only internal note to a ticket. Notes are not visible to the client and do not trigger email notifications. It is categorised as a Write tool in the Whmcs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Whmcs MCP server in PolicyLayer and add a rule for whmcs_add_ticket_note: 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 Whmcs. Nothing to install.
whmcs_add_ticket_note 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 whmcs_add_ticket_note 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 whmcs_add_ticket_note. 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.
whmcs_add_ticket_note is provided by the Whmcs MCP server (scarecr0w12/whmcs-mcp-tool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Whmcs, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
62 Whmcs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.