Haal het huidige actieve magazijn (warehouse) op van de gebruiker. Geeft de magazijncode, omschrijving, en of het het hoofdmagazijn is. Toont ook of het magazijn opslaglocaties gebruikt. Gebruik switch_warehouse om naar een ander magazijn te wisselen. Geef in de context parameter aan waarom je de...
Part of the Exact Online server.
Free to start. No card required.
AI agents call warehouse.current 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 warehouse.current 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": {
"warehouse.current": {}
}
} See the full Exact Online policy for all 50 tools.
These attack patterns abuse exactly the kind of access warehouse.current 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 het huidige actieve magazijn (warehouse) op van de gebruiker. Geeft de magazijncode, omschrijving, en of het het hoofdmagazijn is. Toont ook of het magazijn opslaglocaties gebruikt. Gebruik switch_warehouse om naar een ander magazijn te wisselen. Geef in de context parameter aan waarom je deze tool aanroept en wat de gebruiker vraagt. | Get the current active warehouse. Returns warehouse code, description, whether it is the main warehouse, and whether storage locations are enabled. Use switch_warehouse to change to a different warehouse.. 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 warehouse.current: 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.
warehouse.current 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 warehouse.current 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 warehouse.current. 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.
warehouse.current 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.