reject_supplier_invoice

Reject a supplier invoice. A comment is required.

SERVERTripletex MCP Server SOURCEadriantr/tripletex-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adriantr-tripletex-mcp/reject-supplier-invoice.md

What reject_supplier_invoice does on Tripletex MCP Server

AI agents use reject_supplier_invoice 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_invoice is rated Medium

Rejecting a supplier invoice is a Write operation because it updates the invoice record's status and processing state. While the action affects financial workflows and accounting records, it is reversible—rejected invoices can typically be resubmitted or the rejection can be overturned by a human accountant.

From the tool's definition Tool name 'reject_supplier_invoice' and description 'Reject a supplier invoice' indicate the tool modifies the state of a supplier invoice (from pending/submitted to rejected status). This is a reversible state change, not a deletion.

Questions about reject_supplier_invoice

What does the reject_supplier_invoice tool do? +

Reject a supplier invoice. A comment is required. It is categorised as a Write tool in the Tripletex MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on reject_supplier_invoice? +

Register the Tripletex MCP Server MCP server in PolicyLayer and add a rule for reject_supplier_invoice: 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 Tripletex MCP Server. Nothing to install.

What risk level is reject_supplier_invoice? +

reject_supplier_invoice is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit reject_supplier_invoice? +

Yes. Add a rate_limit block to the reject_supplier_invoice 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.

How do I block reject_supplier_invoice completely? +

Set action: deny in the PolicyLayer policy for reject_supplier_invoice. 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.

What MCP server provides reject_supplier_invoice? +

reject_supplier_invoice is provided by the Tripletex MCP Server MCP server (adriantr/tripletex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Tripletex MCP Server, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Tripletex MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.