reach_removeContactsFromATagV1
Remove a tag from many contacts at once. Pass contact_uuids to target specific contacts, or all_contacts to target every contact in the profile. The work is queued, so a success response means it was accepted rather than finished. The tag itself and the contacts are not deleted.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/reach-removecontactsfromatagv1.md
What reach_removeContactsFromATagV1 does on Hostinger Api
AI agents use reach_removeContactsFromATagV1 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 |
profileUuid | string | Yes | Profile uuid parameter |
Parameters from the server's own tool schema.
Why reach_removeContactsFromATagV1 is rated Medium
Removes tag associations from contacts reversibly; contacts and tags remain intact.
From the tool's definition Remove a tag from many contacts at once
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs reach_removeContactsFromATagV1 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_removeContactsFromATagV1, this is the rule to start with:
reach_removeContactsFromATagV1 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every reach_removeContactsFromATagV1 call is checked against it from then on.
Questions about reach_removeContactsFromATagV1
Remove a tag from many contacts at once. Pass contact_uuids to target specific contacts, or all_contacts to target every contact in the profile. The work is queued, so a success response means it was accepted rather than finished. The tag itself and the contacts are not 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.
reach_removeContactsFromATagV1 accepts 2 parameters: tagUuid, profileUuid. Required: tagUuid, 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_removeContactsFromATagV1: 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_removeContactsFromATagV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reach_removeContactsFromATagV1 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_removeContactsFromATagV1. 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_removeContactsFromATagV1 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.
This server
Across the catalogue