reach_deleteAProfileContactV1
Permanently delete a contact from a profile. The contact is removed together with its custom field values and tag assignments.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/reach-deleteaprofilecontactv1.md
What reach_deleteAProfileContactV1 does on Hostinger Api
AI agents call reach_deleteAProfileContactV1 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 |
|---|---|---|---|
contactUuid | string | Yes | Contact uuid parameter |
profileUuid | string | Yes | Profile uuid parameter |
Parameters from the server's own tool schema.
Why reach_deleteAProfileContactV1 is rated Critical
Irreversibly deletes contact records and associated data without recovery option.
From the tool's definition Permanently delete a contact, custom field values, tag assignments.
Attacks that exploit this kind of access
The rule that runs reach_deleteAProfileContactV1 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_deleteAProfileContactV1, this is the rule to start with:
reach_deleteAProfileContactV1 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_deleteAProfileContactV1 call is checked against it from then on.
Questions about reach_deleteAProfileContactV1
Permanently delete a contact from a profile. The contact is removed together with its custom field values and tag assignments. 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_deleteAProfileContactV1 accepts 2 parameters: contactUuid, profileUuid. Required: contactUuid, 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_deleteAProfileContactV1: 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_deleteAProfileContactV1 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_deleteAProfileContactV1 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_deleteAProfileContactV1. 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_deleteAProfileContactV1 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