get_invoice
Get a single outgoing invoice by ID.
This record as markdown: /tools/adriantr-tripletex-mcp/get-invoice.md
What get_invoice does on Tripletex MCP Server
AI agents call get_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.
Why get_invoice is rated Low
This tool retrieves invoice information by ID, which is a read-only query operation. It accesses existing data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is low—an agent retrieving invoice data cannot cause financial damage, data loss, or trigger unwanted transactions.
From the tool's definition Tool name 'get_invoice' and description 'Get a single outgoing invoice by ID' indicate retrieval of existing invoice data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_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_invoice, this is the rule to start with:
get_invoice is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tripletex MCP Server, apply this rule, and every get_invoice call is checked against it from then on.
Questions about get_invoice
Get a single outgoing 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.
Register the Tripletex MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_invoice is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
This server
Across the catalogue