hosting_createAccountDatabaseRemoteConnectionV1

Allows a remote host to connect to the specified database. Provide an IPv4/IPv6 address, or "%" to allow any host. The database name must be the full name returned by the list databases endpoint.

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 33 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-createaccountdatabaseremoteconnectionv1.md

WHAT IT DOES

What hosting_createAccountDatabaseRemoteConnectionV1 does on Hostinger Api

AI agents use hosting_createAccountDatabaseRemoteConnectionV1 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
`ip`	string	Yes	Remote host to allow: an IPv4/IPv6 address, or "%" for any host.
`name`	string	Yes	Full database name as returned by the list databases endpoint.
`username`	string	Yes	username parameter

Parameters from the server's own tool schema.

RISK

Why hosting_createAccountDatabaseRemoteConnectionV1 is rated Medium

This tool creates new database remote connection configurations, which modifies security policies and access control lists for a database. While it doesn't directly access or delete data, it reversibly changes database connectivity settings. This is a Write operation because it creates/modifies configuration state.

From the tool's definition Tool description states 'Allows a remote host to connect to the specified database' by accepting IPv4/IPv6 addresses or wildcards to configure database access permissions. This creates or modifies database connection rules and access controls.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hosting_createAccountDatabaseRemoteConnectionV1 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 hosting_createAccountDatabaseRemoteConnectionV1, this is the rule to start with:

hosting_createAccountDatabaseRemoteConnectionV1 Rate-limited

hosting_createAccountDatabaseRemoteConnectionV1 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hosting_createAccountDatabaseRemoteConnectionV1": {
      "limits": [
        {
          "counter": "hosting_createaccountdatabaseremoteconnectionv1_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every hosting_createAccountDatabaseRemoteConnectionV1 call is checked against it from then on.

FAQ

Questions about hosting_createAccountDatabaseRemoteConnectionV1

What does the hosting_createAccountDatabaseRemoteConnectionV1 tool do? +

Allows a remote host to connect to the specified database. Provide an IPv4/IPv6 address, or "%" to allow any host. The database name must be the full name returned by the list databases endpoint. 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.

What parameters does hosting_createAccountDatabaseRemoteConnectionV1 accept? +

hosting_createAccountDatabaseRemoteConnectionV1 accepts 3 parameters: ip, name, username. Required: ip, name, username. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hosting_createAccountDatabaseRemoteConnectionV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for hosting_createAccountDatabaseRemoteConnectionV1: 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.

What risk level is hosting_createAccountDatabaseRemoteConnectionV1? +

hosting_createAccountDatabaseRemoteConnectionV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hosting_createAccountDatabaseRemoteConnectionV1? +

Yes. Add a rate_limit block to the hosting_createAccountDatabaseRemoteConnectionV1 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.

How do I block hosting_createAccountDatabaseRemoteConnectionV1 completely? +

Set action: deny in the PolicyLayer policy for hosting_createAccountDatabaseRemoteConnectionV1. 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.

What MCP server provides hosting_createAccountDatabaseRemoteConnectionV1? +

hosting_createAccountDatabaseRemoteConnectionV1 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.

KEEP EXPLORING

More on Hostinger Api, and thousands of servers like it.

This server

All 258 Hostinger Api tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →