AI agents call list_vouchers 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 and displays existing vouchers/journal entries from the accounting system. It has no side effects—it does not create, modify, delete, or execute any operations. The optional financial year filter is a query parameter that narrows the read scope. Classification as Read is appropriate with low severity due to the read-only nature and minimal risk of misuse by an AI agent.
From the tool's definition Tool name 'list_vouchers' and description 'List journal entries/vouchers' indicate a retrieval operation with optional filtering. The verb 'list' is a classic read-only operation that queries data without modification.
Attacks that exploit this kind of access
List journal entries/vouchers. Optionally filter by financial year. 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 list_vouchers: 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.
list_vouchers 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 list_vouchers 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 list_vouchers. 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.
list_vouchers 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 →