Get movement history for up to 10 documents including statuses and timestamps. Doc 1.2 identifies InternetDocument numbers as the primary shipment identifiers, which this endpoint accepts in batches.
AI agents call get_document_movement 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 tracking history for shipments. It retrieves data (movement history, statuses, timestamps) without side effects. The action is read-only: no data is created, modified, deleted, or financial transactions are initiated. Severity is low because exposure of shipment tracking data has limited blast radius—it reveals logistics status but not sensitive financial or personal information at scale.
From the tool's definition Tool description states 'Get movement history' and 'accepts in batches' — purely retrieval of shipment tracking data with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get movement history for up to 10 documents including statuses and timestamps. Doc 1.2 identifies InternetDocument numbers as the primary shipment identifiers, which this endpoint accepts in batches. 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 get_document_movement: 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.
get_document_movement 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 get_document_movement 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 get_document_movement. 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.
get_document_movement 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 →