List Nova Poshta warehouses (branches, postomats, pickup points) via Address/getWarehouses (doc 1.5). Docs emphasize caching the branch directory daily to leverage schedule arrays, max weight limits, and warehouse types without re-fetching thousands of rows. IMPORTANT: Always use limit parameter ...
AI agents call address_get_warehouses to retrieve information from Novaposhta without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval operation that queries Nova Poshta's warehouse directory. It has no side effects—it only reads and returns warehouse information. The emphasis on caching and pagination further confirms it is a non-destructive, read-only query. No reversible modifications, code execution, deletions, or financial transactions are involved.
From the tool's definition Tool name and description emphasize 'List' and retrieval functionality ('getWarehouses'). The description explicitly recommends caching and limiting response size, with no mention of creating, modifying, deleting, or executing operations.
Attacks that exploit this kind of access
List Nova Poshta warehouses (branches, postomats, pickup points) via Address/getWarehouses (doc 1.5). Docs emphasize caching the branch directory daily to leverage schedule arrays, max weight limits, and warehouse types without re-fetching thousands of rows. IMPORTANT: Always use limit parameter (recommended: 10-20) to avoid large responses. It is categorised as a Read tool in the Novaposhta MCP Server, which means it retrieves data without modifying state.
Register the Novaposhta MCP server in PolicyLayer and add a rule for address_get_warehouses: 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 Novaposhta. Nothing to install.
address_get_warehouses 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 address_get_warehouses 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 address_get_warehouses. 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.
address_get_warehouses is provided by the Novaposhta MCP server (@shopana/novaposhta-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 →