domains_enableDomainLockV1
Enable domain lock for the domain. When domain lock is enabled, the domain cannot be transferred to another registrar without first disabling the lock. Use this endpoint to secure domains against unauthorized transfers.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/domains-enabledomainlockv1.md
What domains_enableDomainLockV1 does on Hostinger Api
AI agents use domains_enableDomainLockV1 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 |
Parameters from the server's own tool schema.
Why domains_enableDomainLockV1 is rated Medium
Enabling domain lock is a configuration change that modifies domain settings but is reversible—the lock can be disabled to restore prior behavior. This places it in Write rather than Destructive. While domain locks prevent unauthorized transfers (protective intent), an AI agent misusing this could lock domains maliciously, disrupting legitimate operations or transfers.
From the tool's definition Tool enables domain lock, modifying domain security settings. Description states 'Enable domain lock for the domain' and explains it prevents transfers. This is a reversible modification (lock can be disabled) rather than deletion or destruction.
Attacks that exploit this kind of access
The rule that runs domains_enableDomainLockV1 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_enableDomainLockV1, this is the rule to start with:
domains_enableDomainLockV1 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_enableDomainLockV1 call is checked against it from then on.
Questions about domains_enableDomainLockV1
Enable domain lock for the domain. When domain lock is enabled, the domain cannot be transferred to another registrar without first disabling the lock. Use this endpoint to secure domains against unauthorized transfers. 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_enableDomainLockV1 accepts 1 parameter: domain. Required: domain. 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_enableDomainLockV1: 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_enableDomainLockV1 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_enableDomainLockV1 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_enableDomainLockV1. 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_enableDomainLockV1 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