reject_supplier_invoices

What reject_supplier_invoices does on Tripletex MCP Server

AI agents use reject_supplier_invoices to create or update resources in Tripletex MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tripletex MCP Server environment.

Why reject_supplier_invoices is rated Medium

Rejecting invoices modifies data state but is not irreversible—rejected invoices can typically be resubmitted or have their status changed. This is a Write operation (modifies data reversibly) rather than Destructive. The blast radius is medium because incorrect rejections of legitimate supplier invoices could disrupt accounting workflows and vendor relationships, but the action itself remains reversible.

From the tool's definition reject_supplier_invoices allows modification of invoice status by rejecting multiple supplier invoices with a required comment. This is a reversible state change (invoices can potentially be re-submitted or their status changed) rather than permanent deletion.

The rule that runs reject_supplier_invoices safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tripletex MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reject_supplier_invoices, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reject_supplier_invoices": {
      "limits": [
        {
          "counter": "reject_supplier_invoices_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about reject_supplier_invoices