agency-hosting_deleteWebsiteDatabaseUserV1
Permanently deletes a database user from an Agency Plan website database, revoking all access it had. The operation is idempotent: deleting a user that does not exist succeeds without error.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-deletewebsitedatabaseuserv1.md
What agency-hosting_deleteWebsiteDatabaseUserV1 does on Hostinger Api
AI agents call agency-hosting_deleteWebsiteDatabaseUserV1 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 |
|---|---|---|---|
website_uid | string | Yes | Agency Plan website UID |
database_name | string | Yes | Full database name as returned by the list databases endpoint. |
database_user_name | string | Yes | Database username as returned by the list databases endpoint. |
Parameters from the server's own tool schema.
Why agency-hosting_deleteWebsiteDatabaseUserV1 is rated Critical
Irreversibly removes database user access with permanent effect; cannot be undone without manual restoration.
From the tool's definition Permanently deletes a database user, revoking all access
Attacks that exploit this kind of access
The rule that runs agency-hosting_deleteWebsiteDatabaseUserV1 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 agency-hosting_deleteWebsiteDatabaseUserV1, this is the rule to start with:
agency-hosting_deleteWebsiteDatabaseUserV1 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 agency-hosting_deleteWebsiteDatabaseUserV1 call is checked against it from then on.
Questions about agency-hosting_deleteWebsiteDatabaseUserV1
Permanently deletes a database user from an Agency Plan website database, revoking all access it had. The operation is idempotent: deleting a user that does not exist succeeds without error. 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.
agency-hosting_deleteWebsiteDatabaseUserV1 accepts 3 parameters: website_uid, database_name, database_user_name. Required: website_uid, database_name, database_user_name. 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 agency-hosting_deleteWebsiteDatabaseUserV1: 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.
agency-hosting_deleteWebsiteDatabaseUserV1 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 agency-hosting_deleteWebsiteDatabaseUserV1 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 agency-hosting_deleteWebsiteDatabaseUserV1. 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.
agency-hosting_deleteWebsiteDatabaseUserV1 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