get_supplier_invoice

Get a single supplier invoice by ID.

SERVERTripletex MCP Server SOURCEadriantr/tripletex-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What get_supplier_invoice does on Tripletex MCP Server

AI agents call get_supplier_invoice to retrieve information from Tripletex MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_supplier_invoice is rated Low

This tool retrieves a single supplier invoice record by its identifier. It performs a read-only query operation that does not create, modify, delete, or execute any actions. While the server manages financial data (invoices), this particular tool only retrieves information without moving money or creating financial obligations.

From the tool's definition Tool name is 'get_supplier_invoice' and description states 'Get a single supplier invoice by ID.' The verb 'get' indicates data retrieval with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_supplier_invoice 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 get_supplier_invoice, this is the rule to start with:

get_supplier_invoice Allowed

get_supplier_invoice is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_supplier_invoice": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tripletex MCP Server, apply this rule, and every get_supplier_invoice call is checked against it from then on.

FAQ

Questions about get_supplier_invoice

What does the get_supplier_invoice tool do? +

Get a single supplier invoice by ID. It is categorised as a Read tool in the Tripletex MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_supplier_invoice? +

Register the Tripletex MCP Server MCP server in PolicyLayer and add a rule for get_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 get_supplier_invoice? +

get_supplier_invoice is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_supplier_invoice? +

Yes. Add a rate_limit block to the get_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 get_supplier_invoice completely? +

Set action: deny in the PolicyLayer policy for get_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 get_supplier_invoice? +

get_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.

KEEP EXPLORING

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

This server

All 31 Tripletex MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →