counterparty_delete

Delete counterparty by reference using Counterparty/delete (doc 1.22). IMPORTANT: Docs explicitly state only Recipient counterparties can be deleted through the API; Sender cleanup must go through your account manager.

Server Novaposhta @shopana/novaposhta-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What counterparty_delete does on Novaposhta

AI agents call counterparty_delete to permanently remove resources in Novaposhta — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why counterparty_delete needs a policy

This tool irreversibly deletes data (counterparty records) from the Nova Poshta system. Even though deletion is restricted to Recipient counterparties only, the operation is destructive and cannot be reversed through normal API operations, making it the most severe category applicable.

From the tool's definition Tool name contains 'delete' and description states 'Delete counterparty by reference'. The action permanently removes a counterparty record, which cannot be undone through the API.

Questions about counterparty_delete

What does the counterparty_delete tool do? +

Delete counterparty by reference using Counterparty/delete (doc 1.22). IMPORTANT: Docs explicitly state only Recipient counterparties can be deleted through the API; Sender cleanup must go through your account manager. It is categorised as a Destructive tool in the Novaposhta MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on counterparty_delete? +

Register the Novaposhta MCP server in PolicyLayer and add a rule for counterparty_delete: 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.

What risk level is counterparty_delete? +

counterparty_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit counterparty_delete? +

Yes. Add a rate_limit block to the counterparty_delete 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.

How do I block counterparty_delete completely? +

Set action: deny in the PolicyLayer policy for counterparty_delete. 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.

What MCP server provides counterparty_delete? +

counterparty_delete 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.