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

reach_listCampaignsV1

Get a paginated list of the campaigns in a profile. Each campaign carries its headline engagement rates. Filter by status to find drafts, scheduled, sending or sent campaigns, keeping in mind that a fully sent campaign has the status publish. By default only regular campaigns are returned - pass ...

SERVERHostinger Api SOURCEhostinger-api-mcp
Low RISK CLASS
Category Read
Parameters 61 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/reach-listcampaignsv1.md

What reach_listCampaignsV1 does on Hostinger Api

AI agents call reach_listCampaignsV1 to retrieve information from Hostinger Api without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
page integer Page number
type string Filter campaigns by type. Defaults to `campaign`, which leaves out the emails sent by automations and the double opt-in confirmations.
status string Filter campaigns by status. A fully sent campaign has the status `publish`. There is no `sent` status, and campaigns can be neither paused nor archived.
per_page integer Number of items per page
profileUuid string Yes Profile uuid parameter
sort_direction string Order campaigns by creation date. Newest first unless set to `asc`.

Parameters from the server's own tool schema.

Why reach_listCampaignsV1 is rated Low

Tool retrieves and filters campaign data without modifying or executing any actions.

From the tool's definition Get a paginated list of campaigns; filter by status; no creation, modification, or deletion.

Questions about reach_listCampaignsV1

What does the reach_listCampaignsV1 tool do? +

Get a paginated list of the campaigns in a profile. Each campaign carries its headline engagement rates. Filter by status to find drafts, scheduled, sending or sent campaigns, keeping in mind that a fully sent campaign has the status publish. By default only regular campaigns are returned - pass type to get the emails sent by automations or the double opt-in confirmations instead. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.

What parameters does reach_listCampaignsV1 accept? +

reach_listCampaignsV1 accepts 6 parameters: page, type, status, per_page, profileUuid, sort_direction. Required: profileUuid. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on reach_listCampaignsV1? +

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

reach_listCampaignsV1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit reach_listCampaignsV1? +

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

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

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