domains_createDomainForwardingV1
Create domain forwarding configuration. Use this endpoint to set up domain redirects to other URLs.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/domains-createdomainforwardingv1.md
What domains_createDomainForwardingV1 does on Hostinger Api
AI agents use domains_createDomainForwardingV1 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 |
|---|---|---|---|
domain | string | Yes | Domain name |
redirect_url | string | Yes | URL to forward domain to |
redirect_type | string | Yes | Redirect type |
Parameters from the server's own tool schema.
Why domains_createDomainForwardingV1 is rated Medium
This tool creates a new domain forwarding configuration, which modifies DNS or domain routing settings. While reversible (forwarding rules can be deleted or updated), it changes the domain's behavior and could redirect traffic to malicious sites if misused by an agent.
From the tool's definition Tool name contains 'create' and description states 'set up domain redirects', indicating creation of a new domain forwarding configuration.
Risk signalsAccepts URL/endpoint input (redirect_url)
Attacks that exploit this kind of access
The rule that runs domains_createDomainForwardingV1 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 domains_createDomainForwardingV1, this is the rule to start with:
domains_createDomainForwardingV1 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 domains_createDomainForwardingV1 call is checked against it from then on.
Questions about domains_createDomainForwardingV1
Create domain forwarding configuration. Use this endpoint to set up domain redirects to other URLs. 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.
domains_createDomainForwardingV1 accepts 3 parameters: domain, redirect_url, redirect_type. Required: domain, redirect_url, redirect_type. 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 domains_createDomainForwardingV1: 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.
domains_createDomainForwardingV1 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 domains_createDomainForwardingV1 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 domains_createDomainForwardingV1. 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.
domains_createDomainForwardingV1 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