This record as markdown: /tools/hostinger-mcp/domains-disable-lock.md
What domains_disable_lock does on Hostinger
AI agents use domains_disable_lock 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_disable_lock is rated Medium
Disabling a registrar lock modifies domain security configuration and makes the domain vulnerable to transfer/hijacking attacks. This is a reversible Write operation (the lock can be re-enabled), not Destructive. However, it carries high severity because an adversary could use this to facilitate domain theft.
From the tool's definition Tool name 'domains_disable_lock' and description 'Disable registrar lock' indicate modification of domain security settings. Registrar lock is a protective mechanism that prevents unauthorized domain transfers.
Attacks that exploit this kind of access
The rule that runs domains_disable_lock 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_disable_lock, this is the rule to start with:
domains_disable_lock 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_disable_lock call is checked against it from then on.
Questions about domains_disable_lock
Disable registrar lock. 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_disable_lock: 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_disable_lock 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_disable_lock 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_disable_lock. 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_disable_lock 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