Haal de volledige historie op van een batchnummer (batch number). Geeft alle voorraadtransacties voor een specifieke batch, inclusief locaties, hoeveelheden en transactietypes (ontvangst, levering, verplaatsing). Optioneel filteren op artikelcode. Gebruik get_stock_info om eerst de batchnummers v...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Exact Online server.
Free to start. No card required.
AI agents call items.batch.history to retrieve information from Exact Online without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though items.batch.history only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"items.batch.history": {}
}
}See the full Exact Online policy for all 50 tools.
These attack patterns abuse exactly the kind of access items.batch.history gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Haal de volledige historie op van een batchnummer (batch number). Geeft alle voorraadtransacties voor een specifieke batch, inclusief locaties, hoeveelheden en transactietypes (ontvangst, levering, verplaatsing). Optioneel filteren op artikelcode. Gebruik get_stock_info om eerst de batchnummers van een artikel te vinden. Ondersteunt paginering: gebruik offset om meer resultaten op te halen als hasMore=true in het antwoord. Geef in de context parameter aan waarom je deze tool aanroept en wat de gebruiker vraagt. | Get full history of a batch number. Returns all stock transactions including locations, quantities and transaction types. Use get_stock_info to find batch numbers for an item first.. It is categorised as a Read tool in the Exact Online MCP Server, which means it retrieves data without modifying state.
Register the Exact Online MCP server in PolicyLayer and add a rule for items.batch.history: 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 Exact Online. Nothing to install.
items.batch.history 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 items.batch.history 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 items.batch.history. 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.
items.batch.history is provided by the Exact Online MCP server (IndustrialIT/LedgerBotje). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 50 Exact Online tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.