AI agents call get_invoice_payments to retrieve information from Fortnox without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical payment information associated with an invoice without creating, modifying, or deleting any data. It is a read-only query operation on accounting data. The low severity reflects that an AI agent misusing this tool cannot cause financial harm, data loss, or unauthorized changes—only information disclosure, which is limited to data already associated with the queried invoice.
From the tool's definition Tool name 'get_invoice_payments' and description 'Check payment status and history for a specific invoice' indicate a retrieval operation. The verb 'Check' and 'get' prefix confirm query-only functionality with no modification or side effects.
Attacks that exploit this kind of access
Check payment status and history for a specific invoice. It is categorised as a Read tool in the Fortnox MCP Server, which means it retrieves data without modifying state.
Register the Fortnox MCP server in PolicyLayer and add a rule for get_invoice_payments: 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 Fortnox. Nothing to install.
get_invoice_payments 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_payments 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_payments. 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_payments is provided by the Fortnox MCP server (proviscale/fortnox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →