reach_listEmailTemplatesV1
Get a list of the email templates in a profile, most recently updated first. Templates are the reusable email bodies a campaign is built from. The list is not paginated and only the metadata is returned - the template content itself is not exposed. Use the uuid of a template as the template_uuid ...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/reach-listemailtemplatesv1.md
What reach_listEmailTemplatesV1 does on Hostinger Api
AI agents call reach_listEmailTemplatesV1 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
profileUuid | string | Yes | Profile uuid parameter |
Parameters from the server's own tool schema.
Why reach_listEmailTemplatesV1 is rated Low
Retrieves email template metadata without side effects or sensitive content exposure.
From the tool's definition Get a list of email templates, metadata only, no content exposed.
Attacks that exploit this kind of access
The rule that runs reach_listEmailTemplatesV1 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_listEmailTemplatesV1, this is the rule to start with:
reach_listEmailTemplatesV1 is read-only, so it stays allowed. 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_listEmailTemplatesV1 call is checked against it from then on.
Questions about reach_listEmailTemplatesV1
Get a list of the email templates in a profile, most recently updated first. Templates are the reusable email bodies a campaign is built from. The list is not paginated and only the metadata is returned - the template content itself is not exposed. Use the uuid of a template as the template_uuid when creating a campaign. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
reach_listEmailTemplatesV1 accepts 1 parameter: profileUuid. Required: 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_listEmailTemplatesV1: 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_listEmailTemplatesV1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the reach_listEmailTemplatesV1 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_listEmailTemplatesV1. 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_listEmailTemplatesV1 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