Create a charge (material, cost, or expense) on a ticket. Used to bill clients for parts, travel, or other non-labor costs.
AI agents use autotask_create_ticket_charge to commit financial operations through Autotask MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool creates billable charges against client tickets, directly committing financial obligations and affecting client billing. Creating charges that bill clients constitutes a financial action, and misuse could result in incorrect or fraudulent charges being applied to client accounts, making it high severity.
From the tool's definition 'Create a charge (material, cost, or expense) on a ticket. Used to bill clients for parts, travel, or other non-labor costs.'
Attacks that exploit this kind of access
Create a charge (material, cost, or expense) on a ticket. Used to bill clients for parts, travel, or other non-labor costs. It is categorised as a Financial tool in the Autotask MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Autotask MCP Server MCP server in PolicyLayer and add a rule for autotask_create_ticket_charge: 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 Autotask MCP Server. Nothing to install.
autotask_create_ticket_charge is a Financial 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 autotask_create_ticket_charge 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 autotask_create_ticket_charge. 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.
autotask_create_ticket_charge is provided by the Autotask MCP Server MCP server (ticnine/autotask-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →