New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

hosting_createDatabaseRemoteConnectionV1

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-createdatabaseremoteconnectionv1.md

What hosting_createDatabaseRemoteConnectionV1 does on Hostinger Api

AI agents use hosting_createDatabaseRemoteConnectionV1 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.

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

Why hosting_createDatabaseRemoteConnectionV1 is rated Medium

This tool creates or modifies database access configuration reversibly (remote connections can be removed), qualifying it as Write rather than Execute or Destructive. However, the severity is high because misconfiguration—such as using '%' to allow any host—could expose sensitive database resources to unauthorized access, creating significant security risk even though the action itself is not irreversible.

From the tool's definition Tool creates a database remote connection by allowing a remote host (via IPv4/IPv6 address or wildcard '%') to connect to a specified database.

Questions about hosting_createDatabaseRemoteConnectionV1

What does the hosting_createDatabaseRemoteConnectionV1 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_createDatabaseRemoteConnectionV1 accept? +

hosting_createDatabaseRemoteConnectionV1 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_createDatabaseRemoteConnectionV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for hosting_createDatabaseRemoteConnectionV1: 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_createDatabaseRemoteConnectionV1? +

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

Can I rate-limit hosting_createDatabaseRemoteConnectionV1? +

Yes. Add a rate_limit block to the hosting_createDatabaseRemoteConnectionV1 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_createDatabaseRemoteConnectionV1 completely? +

Set action: deny in the PolicyLayer policy for hosting_createDatabaseRemoteConnectionV1. 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_createDatabaseRemoteConnectionV1? +

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger Api's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.