New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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.

SERVERHostinger Api SOURCEhostinger-api-mcp
Medium RISK CLASS
Category Write
Parameters 73 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-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.

ParameterTypeRequiredDescription
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.

Questions about reach_createADraftCampaignV1

What does the reach_createADraftCampaignV1 tool do? +

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.

What parameters does reach_createADraftCampaignV1 accept? +

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.

How do I enforce a policy on reach_createADraftCampaignV1? +

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.

What risk level is reach_createADraftCampaignV1? +

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

Can I rate-limit reach_createADraftCampaignV1? +

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.

How do I block reach_createADraftCampaignV1 completely? +

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.

What MCP server provides reach_createADraftCampaignV1? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger Api's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.