Track multiple Nova Poshta documents with organized results and statistics via TrackingDocument/getStatusDocuments (doc 1.2). Returns successful/failed tracking attempts with delivery statistics (delivered, in-transit, at-warehouse counts). More convenient than track_multiple_documents for batch ...
AI agents call track_multiple 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 tool queries the status of delivery documents and compiles statistics—a pure read operation with no side effects. It does not create, modify, delete, or execute any operations on the documents themselves; it only retrieves their current tracking status. The low severity reflects minimal blast radius: misuse would only expose tracking information, not modify shipments or cause financial harm.
From the tool's definition Tool 'track_multiple' retrieves tracking status and statistics for Nova Poshta documents. The description explicitly states it 'Track[s] multiple Nova Poshta documents' and 'Returns successful/failed tracking attempts with delivery statistics'.
Attacks that exploit this kind of access
Track multiple Nova Poshta documents with organized results and statistics via TrackingDocument/getStatusDocuments (doc 1.2). Returns successful/failed tracking attempts with delivery statistics (delivered, in-transit, at-warehouse counts). More convenient than track_multiple_documents for batch operations. 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 track_multiple: 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.
track_multiple 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 track_multiple 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 track_multiple. 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.
track_multiple 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 →