gross_pay_items_update
AI agents use gross_pay_items_update to commit financial operations through ServiceTitan MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
gross_pay_items_update moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Attacks that exploit this kind of access
gross_pay_items_update. It is categorised as a Financial tool in the ServiceTitan MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the ServiceTitan MCP Server MCP server in PolicyLayer and add a rule for gross_pay_items_update: 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 ServiceTitan MCP Server. Nothing to install.
gross_pay_items_update 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 gross_pay_items_update 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 gross_pay_items_update. 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.
gross_pay_items_update is provided by the ServiceTitan MCP Server MCP server (jordandalton/servicetitanmcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.