This record as markdown: /tools/hostinger-mcp/hosting-db-list.md
What hosting_db_list does on Hostinger
AI agents call hosting_db_list to retrieve information from Hostinger without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why hosting_db_list is rated Low
This tool retrieves and lists existing database information without creating, modifying, deleting, or executing operations. It is a read-only query operation with minimal blast radius if misused by an AI agent—at worst, it exposes database metadata that may already be accessible through other means.
From the tool's definition Tool name 'hosting_db_list' and description 'List databases for a hosting account' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs hosting_db_list 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 hosting_db_list, this is the rule to start with:
hosting_db_list is read-only, so it stays allowed. 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 hosting_db_list call is checked against it from then on.
Questions about hosting_db_list
List databases for a hosting account. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.
Register the Hostinger MCP server in PolicyLayer and add a rule for hosting_db_list: 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.
hosting_db_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hosting_db_list 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 hosting_db_list. 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.
hosting_db_list 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