agency_db_delete_user

Delete a database user.

SERVERHostinger SOURCEidugeni/hostinger-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/agency-db-delete-user.md

WHAT IT DOES

What agency_db_delete_user does on Hostinger

AI agents call agency_db_delete_user to permanently remove resources in Hostinger, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why agency_db_delete_user is rated Critical

This tool performs an irreversible destructive action—deletion of a database user account. Once deleted, the user account and its associated permissions are permanently removed and cannot be recovered through normal operations. This is categorized as Destructive rather than Write because deletion is not reversible.

From the tool's definition Tool name: agency_db_delete_user. Description: 'Delete a database user.' The verb 'delete' indicates irreversible removal of an object (a database user account).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs agency_db_delete_user safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agency_db_delete_user, this is the rule to start with:

agency_db_delete_user Hidden

agency_db_delete_user 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_db_delete_user"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about agency_db_delete_user

What does the agency_db_delete_user tool do? +

Delete a database user. It is categorised as a Destructive tool in the Hostinger MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on agency_db_delete_user? +

Register the Hostinger MCP server in PolicyLayer and add a rule for agency_db_delete_user: 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. Nothing to install.

What risk level is agency_db_delete_user? +

agency_db_delete_user 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_db_delete_user? +

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

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

agency_db_delete_user is provided by the Hostinger MCP server (idugeni/hostinger-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, and thousands of servers like it.

This server

All 284 Hostinger tools → Critical-risk tools on this server →

Across the catalogue

delete_mysql_user on cPanel MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →