agency-hosting_createWebsiteDatabaseV1
Creates a MySQL database with a dedicated user for an Agency Plan website. The database name, username, and password must all be provided by the caller.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/agency-hosting-createwebsitedatabasev1.md
What agency-hosting_createWebsiteDatabaseV1 does on Hostinger Api
AI agents use agency-hosting_createWebsiteDatabaseV1 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 |
|---|---|---|---|
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 | Database name to create (alphanumeric characters). |
database_user | string | Yes | Database username to create alongside the database (alphanumeric characters). |
Parameters from the server's own tool schema.
Why agency-hosting_createWebsiteDatabaseV1 is rated Medium
Creates persistent database infrastructure; high blast radius if credentials or names misused by agent.
From the tool's definition Creates a MySQL database with dedicated user; irreversible creation modifies infrastructure.
Risk signalsHandles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs agency-hosting_createWebsiteDatabaseV1 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_createWebsiteDatabaseV1, this is the rule to start with:
agency-hosting_createWebsiteDatabaseV1 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every agency-hosting_createWebsiteDatabaseV1 call is checked against it from then on.
Questions about agency-hosting_createWebsiteDatabaseV1
Creates a MySQL database with a dedicated user for an Agency Plan website. The database name, username, and password must all be provided by the caller. 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.
agency-hosting_createWebsiteDatabaseV1 accepts 4 parameters: 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.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for agency-hosting_createWebsiteDatabaseV1: 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_createWebsiteDatabaseV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the agency-hosting_createWebsiteDatabaseV1 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_createWebsiteDatabaseV1. 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_createWebsiteDatabaseV1 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.
This server
Across the catalogue