hosting_deleteAccountDatabaseRemoteConnectionV1
Permanently removes a remote-access rule, revoking the given host's remote access to the database. Identify the rule with the required ip query parameter (the IPv4/IPv6 address, or "%", exactly as returned by the list remote connections endpoint). The database name must be the full name returned ...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-deleteaccountdatabaseremoteconnectionv1.md
What hosting_deleteAccountDatabaseRemoteConnectionV1 does on Hostinger Api
AI agents call hosting_deleteAccountDatabaseRemoteConnectionV1 to permanently remove resources in Hostinger Api, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
ip | string | Yes | Remote host to revoke: the IPv4/IPv6 address, or "%", exactly as returned by the list remote connections endpoint. |
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_deleteAccountDatabaseRemoteConnectionV1 is rated Critical
The tool performs an irreversible deletion operation ('Permanently removes') of a database remote connection rule. While not directly deleting data, this is a destructive action that cannot be undone and removes access configurations. The blast radius is high because misconfiguration could revoke legitimate remote database access, disrupting application connectivity.
From the tool's definition Permanently removes a remote-access rule, revoking the given host's remote access to the database.
Attacks that exploit this kind of access
The rule that runs hosting_deleteAccountDatabaseRemoteConnectionV1 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_deleteAccountDatabaseRemoteConnectionV1, this is the rule to start with:
hosting_deleteAccountDatabaseRemoteConnectionV1 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every hosting_deleteAccountDatabaseRemoteConnectionV1 call is checked against it from then on.
Questions about hosting_deleteAccountDatabaseRemoteConnectionV1
Permanently removes a remote-access rule, revoking the given host's remote access to the database. Identify the rule with the required ip query parameter (the IPv4/IPv6 address, or "%", exactly as returned by the list remote connections endpoint). The database name must be the full name returned by the list databases endpoint. It is categorised as a Destructive tool in the Hostinger Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
hosting_deleteAccountDatabaseRemoteConnectionV1 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.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for hosting_deleteAccountDatabaseRemoteConnectionV1: 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.
hosting_deleteAccountDatabaseRemoteConnectionV1 is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the hosting_deleteAccountDatabaseRemoteConnectionV1 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_deleteAccountDatabaseRemoteConnectionV1. 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_deleteAccountDatabaseRemoteConnectionV1 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