agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1

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.

SERVERHostinger Api SOURCEhostinger-api-mcp

Critical RISK CLASS

Category Destructive

Parameters 33 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1 does on Hostinger Api

AI agents call agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1 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.

RISK

Why agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1 is rated Critical

An AI agent that decides to call agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1 doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Hostinger Api is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1 Hidden

agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1

What does the agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1 tool do? +

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.

What parameters does agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1 accept? +

agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1 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.

How do I enforce a policy on agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1? +

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

agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1 is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1? +

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

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

agency-hosting_deleteAgencyPlanWebsiteDatabaseUserV1 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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →