contact_person_update · Novaposhta MCP: Risk & Policy

WHAT IT DOES

What contact_person_update does on Novaposhta

AI agents use contact_person_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.

WHY IT NEEDS A POLICY

Why contact_person_update needs a policy

The tool modifies existing contact person information (full profiles for legal entities, phone numbers for private persons) but does not irreversibly delete data. The write operation is reversible and bounded by business logic constraints (only before waybill issuance).

From the tool's definition Tool name 'contact_person_update' and description explicitly states 'Update existing contact person details', which performs modification operations on stored contact data. This is a write operation that creates reversible changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

contact_person_update Rate-limited

contact_person_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "contact_person_update": {
      "limits": [
        {
          "counter": "contact_person_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Novaposhta, so you can run agents against it safely.

FAQ

Questions about contact_person_update

What does the contact_person_update tool do? +

Update existing contact person details via ContactPerson/update (doc 1.27). Only legal entities may edit full profiles, private persons can change phone only, and edits are allowed solely before a waybill is issued for that counterparty. 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.

How do I enforce a policy on contact_person_update? +

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

What risk level is contact_person_update? +

contact_person_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit contact_person_update? +

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

How do I block contact_person_update completely? +

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

What MCP server provides contact_person_update? +

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