contact_person_delete

Delete contact person by reference using ContactPerson/delete (doc 1.27). Nova Poshta allows deletions via API only for legal entities and only until the contact was used on an Internet document.

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

What contact_person_delete does on Novaposhta

AI agents call contact_person_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 contact_person_delete needs a policy

This tool irreversibly deletes contact person data from the Nova Poshta system. Although deletions are restricted to certain conditions (legal entities, pre-document-usage), the operation itself is destructive and cannot be undone. An AI agent misusing this could permanently remove critical contact records, disrupting business operations and customer relationships.

From the tool's definition Tool name explicitly contains 'delete'. Description states it performs deletion via API and references 'ContactPerson/delete' endpoint.

Questions about contact_person_delete

What does the contact_person_delete tool do? +

Delete contact person by reference using ContactPerson/delete (doc 1.27). Nova Poshta allows deletions via API only for legal entities and only until the contact was used on an Internet document. 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 contact_person_delete? +

Register the Novaposhta MCP server in PolicyLayer and add a rule for contact_person_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 contact_person_delete? +

contact_person_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 contact_person_delete? +

Yes. Add a rate_limit block to the contact_person_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 contact_person_delete completely? +

Set action: deny in the PolicyLayer policy for contact_person_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 contact_person_delete? +

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