horizons_getWebsiteV1

SERVERHostinger Api SOURCEhostinger-api-mcp

Low RISK CLASS

Category Read

Parameters 11 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/horizons-getwebsitev1.md

WHAT IT DOES

What horizons_getWebsiteV1 does on Hostinger Api

AI agents call horizons_getWebsiteV1 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
`websiteId`	string	Yes	The website ID

Parameters from the server's own tool schema.

RISK

Why horizons_getWebsiteV1 is rated Low

This tool retrieves data (a website editing link/URL) without side effects. While the description mentions that users CAN edit websites via the returned link, the tool itself only performs a Read operation by fetching and returning the link. The actual editing would occur outside this tool in the Hostinger Horizons interface.

From the tool's definition Tool description states it 'Get[s] a link for the user to edit their website' and 'Websites can only be edited in Hostinger Horizons interface in the provided website URL.' The tool retrieves/returns a URL link; it does not itself perform modifications,…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs horizons_getWebsiteV1 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 horizons_getWebsiteV1, this is the rule to start with:

horizons_getWebsiteV1 Allowed

horizons_getWebsiteV1 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "horizons_getWebsiteV1": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every horizons_getWebsiteV1 call is checked against it from then on.

FAQ

Questions about horizons_getWebsiteV1

What does the horizons_getWebsiteV1 tool do? +

Get a link for the user to edit their website in Hostinger Horizons interface.\n Use this tool when user wants to modify, edit or add new features to an existing website.\n Websites can only be edited in Hostinger Horizons interface in the provided website URL. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.

What parameters does horizons_getWebsiteV1 accept? +

horizons_getWebsiteV1 accepts 1 parameter: websiteId. Required: websiteId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on horizons_getWebsiteV1? +

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

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

Can I rate-limit horizons_getWebsiteV1? +

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

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

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

KEEP EXPLORING

More on Hostinger Api, and thousands of servers like it.

This server

All 258 Hostinger Api tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →