agency-hosting_createAgencyPlanWebsiteDatabaseUserV1

Creates a user for an existing database on an Agency Plan website. Each database supports a single non-system user; creating a user for a database that already has one fails.

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 54 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/agency-hosting-createagencyplanwebsitedatabaseuserv1.md

WHAT IT DOES

What agency-hosting_createAgencyPlanWebsiteDatabaseUserV1 does on Hostinger Api

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

Parameter	Type	Required	Description
`host`	string	—	Host the user connects from (IPv4, IPv6, % wildcard, or localhost). Defaults to localhost.
`password`	string	Yes	Password for the database user (requires mixed case, letters, and numbers).
`website_uid`	string	Yes	Agency Plan website UID
`database_name`	string	Yes	Full database name as returned by the list databases endpoint.
`database_user`	string	Yes	Database username to create (alphanumeric and underscores).

Parameters from the server's own tool schema.

RISK

Why agency-hosting_createAgencyPlanWebsiteDatabaseUserV1 is rated Medium

An AI agent can call agency-hosting_createAgencyPlanWebsiteDatabaseUserV1 faster than any human can review: one bad instruction and it creates or modifies resources in Hostinger Api by the hundred, each call as confident as the last.

Risk signalsAccepts URL/endpoint input (host) · Handles credentials or secrets (password)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

agency-hosting_createAgencyPlanWebsiteDatabaseUserV1 Rate-limited

agency-hosting_createAgencyPlanWebsiteDatabaseUserV1 stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "agency-hosting_createAgencyPlanWebsiteDatabaseUserV1": {
      "limits": [
        {
          "counter": "agency-hosting_createagencyplanwebsitedatabaseuserv1_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_createAgencyPlanWebsiteDatabaseUserV1 call is checked against it from then on.

FAQ

Questions about agency-hosting_createAgencyPlanWebsiteDatabaseUserV1

What does the agency-hosting_createAgencyPlanWebsiteDatabaseUserV1 tool do? +

Creates a user for an existing database on an Agency Plan website. Each database supports a single non-system user; creating a user for a database that already has one fails. 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 agency-hosting_createAgencyPlanWebsiteDatabaseUserV1 accept? +

agency-hosting_createAgencyPlanWebsiteDatabaseUserV1 accepts 5 parameters: host, password, website_uid, database_name, database_user. Required: password, website_uid, database_name, database_user. The full parameter table on this page comes from the server's own tool schema.

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

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

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

Can I rate-limit agency-hosting_createAgencyPlanWebsiteDatabaseUserV1? +

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

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

agency-hosting_createAgencyPlanWebsiteDatabaseUserV1 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 →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →