reach_removeAContactFromATagV1

Remove a tag from a single contact. Unlike the bulk endpoint this is applied immediately rather than queued. Neither the tag nor the contact is deleted.

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 33 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-removeacontactfromatagv1.md

WHAT IT DOES

What reach_removeAContactFromATagV1 does on Hostinger Api

AI agents use reach_removeAContactFromATagV1 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
`tagUuid`	string	Yes	Tag uuid parameter
`contactUuid`	string	Yes	Contact uuid parameter
`profileUuid`	string	Yes	Profile uuid parameter

Parameters from the server's own tool schema.

RISK

Why reach_removeAContactFromATagV1 is rated Medium

Reversibly removes a tag association from a contact; no deletion of records occurs.

From the tool's definition Remove a tag from a single contact; neither tag nor contact is deleted

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs reach_removeAContactFromATagV1 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_removeAContactFromATagV1, this is the rule to start with:

reach_removeAContactFromATagV1 Rate-limited

reach_removeAContactFromATagV1 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_removeAContactFromATagV1": {
      "limits": [
        {
          "counter": "reach_removeacontactfromatagv1_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_removeAContactFromATagV1 call is checked against it from then on.

FAQ

Questions about reach_removeAContactFromATagV1

What does the reach_removeAContactFromATagV1 tool do? +

Remove a tag from a single contact. Unlike the bulk endpoint this is applied immediately rather than queued. Neither the tag nor the contact is deleted. 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_removeAContactFromATagV1 accept? +

reach_removeAContactFromATagV1 accepts 3 parameters: tagUuid, contactUuid, profileUuid. Required: tagUuid, contactUuid, profileUuid. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on reach_removeAContactFromATagV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for reach_removeAContactFromATagV1: 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_removeAContactFromATagV1? +

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

Can I rate-limit reach_removeAContactFromATagV1? +

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

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

reach_removeAContactFromATagV1 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 →