domains_update_forwarding
Update domain forwarding/redirect.
This record as markdown: /tools/hostinger-mcp/domains-update-forwarding.md
What domains_update_forwarding does on Hostinger
AI agents use domains_update_forwarding to create or update resources in Hostinger, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger environment.
Why domains_update_forwarding is rated Medium
This tool modifies domain forwarding settings, which is a reversible change to domain configuration. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), involve financial transactions (would be Financial), or merely read data (would be Read).
From the tool's definition Tool name 'domains_update_forwarding' and description 'Update domain forwarding/redirect' indicate modification of existing domain configuration. The verb 'update' and the domain forwarding/redirect functionality show reversible data modification.
Attacks that exploit this kind of access
The rule that runs domains_update_forwarding safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For domains_update_forwarding, this is the rule to start with:
domains_update_forwarding 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, apply this rule, and every domains_update_forwarding call is checked against it from then on.
Questions about domains_update_forwarding
Update domain forwarding/redirect. It is categorised as a Write tool in the Hostinger MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hostinger MCP server in PolicyLayer and add a rule for domains_update_forwarding: 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. Nothing to install.
domains_update_forwarding 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_update_forwarding 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_update_forwarding. 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_update_forwarding is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger, and thousands of servers like it.
This server
Across the catalogue