Update existing counterparty address with Address/update (doc 1.25). Nova Poshta docs stress you can edit an address only until a waybill is created with it, so run this immediately after address creation.
AI agents use address_update to create or update resources in Novaposhta — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Novaposhta environment.
This tool creates or modifies address data reversibly. While it carries constraints (cannot edit after waybill creation), the action itself is a write operation that can be undone or corrected by subsequent updates. Severity is medium because misuse could corrupt address data in a shipping/logistics system, affecting order fulfillment, but the impact is localized to address records and reversible.
From the tool's definition Tool name contains 'update'; description states 'Update existing counterparty address' and 'edit an address', which are reversible modifications. The tool modifies data (address records) but does not delete or irreversibly alter them.
Attacks that exploit this kind of access
Update existing counterparty address with Address/update (doc 1.25). Nova Poshta docs stress you can edit an address only until a waybill is created with it, so run this immediately after address creation. It is categorised as a Write tool in the Novaposhta MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Novaposhta MCP server in PolicyLayer and add a rule for address_update: 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_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the address_update 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_update. 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_update 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 →