reach_updateAContactFieldV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 43 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/reach-updateacontactfieldv1.md

WHAT IT DOES

What reach_updateAContactFieldV1 does on Hostinger Api

AI agents use reach_updateAContactFieldV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.

Parameter	Type	Required	Description
`label`	string	Yes	label parameter
`options`	array	—	Replaces the option set when provided. Entries carrying a uuid are kept and relabelled, entries without one are created, and any existing option missing from th
`fieldUuid`	string	Yes	Contact field uuid parameter
`profileUuid`	string	Yes	Profile uuid parameter

Parameters from the server's own tool schema.

RISK

Why reach_updateAContactFieldV1 is rated Medium

Modifies contact data and deletes option values irreversibly, affecting multiple records with high blast radius.

From the tool's definition Rename custom contact field, replace option set, delete existing options and values.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs reach_updateAContactFieldV1 safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reach_updateAContactFieldV1, this is the rule to start with:

reach_updateAContactFieldV1 Rate-limited

reach_updateAContactFieldV1 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": {
    "reach_updateAContactFieldV1": {
      "limits": [
        {
          "counter": "reach_updateacontactfieldv1_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every reach_updateAContactFieldV1 call is checked against it from then on.

FAQ

Questions about reach_updateAContactFieldV1

What does the reach_updateAContactFieldV1 tool do? +

Rename a custom contact field and, for the choice types, replace its option set. Options carrying a uuid are kept and relabelled, options without one are created, and any existing option left out of the list is deleted along with the values contacts hold for it. The field type and slug cannot be changed. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does reach_updateAContactFieldV1 accept? +

reach_updateAContactFieldV1 accepts 4 parameters: label, options, fieldUuid, profileUuid. Required: label, fieldUuid, profileUuid. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on reach_updateAContactFieldV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for reach_updateAContactFieldV1: 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 Hostinger Api. Nothing to install.

What risk level is reach_updateAContactFieldV1? +

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

Can I rate-limit reach_updateAContactFieldV1? +

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

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

reach_updateAContactFieldV1 is provided by the Hostinger Api MCP server (hostinger-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hostinger Api, and thousands of servers like it.

This server

All 382 Hostinger Api tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →