reach_createADraftCampaignV1
Create a campaign in a profile. The campaign is created as a draft, so nothing is sent and no contact is touched. It has no audience yet either - targeting and scheduling are not part of this request, the draft is finished and sent from the Reach interface.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/reach-createadraftcampaignv1.md
What reach_createADraftCampaignV1 does on Hostinger Api
AI agents use reach_createADraftCampaignV1 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 |
|---|---|---|---|
title | string | — | Name the campaign is listed under. Not shown to the recipients. |
subject | string | — | Subject line of the email. |
metadata | object | — | Extra campaign fields. Any key outside the listed ones is rejected. |
profileUuid | string | Yes | Profile uuid parameter |
sender_name | string | Yes | From name shown to the recipients. |
sender_email | string | Yes | From address of the campaign. Its domain has to be verified on the profile before the campaign can be sent. |
template_uuid | string | — | Template to send, as returned by the template endpoints. Can be left out and attached later, but the campaign cannot be sent without one. |
Parameters from the server's own tool schema.
Why reach_createADraftCampaignV1 is rated Medium
Creates draft campaign data reversibly without side effects or audience targeting.
From the tool's definition Create a campaign in a profile as a draft; nothing sent, no contact touched.
Attacks that exploit this kind of access
The rule that runs reach_createADraftCampaignV1 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_createADraftCampaignV1, this is the rule to start with:
reach_createADraftCampaignV1 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_createADraftCampaignV1 call is checked against it from then on.
Questions about reach_createADraftCampaignV1
Create a campaign in a profile. The campaign is created as a draft, so nothing is sent and no contact is touched. It has no audience yet either - targeting and scheduling are not part of this request, the draft is finished and sent from the Reach interface. 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_createADraftCampaignV1 accepts 7 parameters: title, subject, metadata, profileUuid, sender_name, sender_email, template_uuid. Required: profileUuid, sender_name, sender_email. 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_createADraftCampaignV1: 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_createADraftCampaignV1 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_createADraftCampaignV1 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_createADraftCampaignV1. 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_createADraftCampaignV1 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