reach_deleteAContactFieldV1
Delete a custom contact field. Every value contacts hold for the field is deleted with it, and for the choice types so are its options. The contacts themselves are not affected.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/reach-deleteacontactfieldv1.md
What reach_deleteAContactFieldV1 does on Hostinger Api
AI agents call reach_deleteAContactFieldV1 to permanently remove resources in Hostinger Api, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
fieldUuid | string | Yes | Contact field uuid parameter |
profileUuid | string | Yes | Profile uuid parameter |
Parameters from the server's own tool schema.
Why reach_deleteAContactFieldV1 is rated Critical
Irreversibly deletes contact field data and all associated values; cannot be undone.
From the tool's definition Delete a custom contact field. Every value contacts hold for the field is deleted.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs reach_deleteAContactFieldV1 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_deleteAContactFieldV1, this is the rule to start with:
reach_deleteAContactFieldV1 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every reach_deleteAContactFieldV1 call is checked against it from then on.
Questions about reach_deleteAContactFieldV1
Delete a custom contact field. Every value contacts hold for the field is deleted with it, and for the choice types so are its options. The contacts themselves are not affected. It is categorised as a Destructive tool in the Hostinger Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
reach_deleteAContactFieldV1 accepts 2 parameters: fieldUuid, profileUuid. Required: fieldUuid, profileUuid. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for reach_deleteAContactFieldV1: 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.
reach_deleteAContactFieldV1 is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the reach_deleteAContactFieldV1 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 reach_deleteAContactFieldV1. 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.
reach_deleteAContactFieldV1 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.
More on Hostinger Api, and thousands of servers like it.
Across the catalogue