hosting_createAccountDatabaseV1

Creates a database with a database user and password for the specified account. The database name and user are automatically prefixed with the account username when needed.

SERVERHostinger Api SOURCEhostinger-api-mcp
Medium RISK CLASS
Category Write
Parameters 55 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/hosting-createaccountdatabasev1.md

What hosting_createAccountDatabaseV1 does on Hostinger Api

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

ParameterTypeRequiredDescription
name string Yes Database name. If the account username prefix is omitted, it is added automatically.
user string Yes Database user. If the account username prefix is omitted, it is added automatically.
password string Yes Database user password.
username string Yes username parameter
website_domain string Yes Website domain assigned to the database.

Parameters from the server's own tool schema.

Why hosting_createAccountDatabaseV1 is rated Medium

This tool creates new resources (database and user) that are reversible through deletion or modification. It does not delete data permanently, execute arbitrary code, or move money, so it falls under Write rather than Destructive, Execute, or Financial. However, severity is high because creating databases could enable data storage for malicious purposes and affects the account's infrastructure.

From the tool's definition Tool description states it 'Creates a database with a database user and password for the specified account' — a clear create operation that modifies the hosting account's data structure.

Risk signalsHandles credentials or secrets (password)

Questions about hosting_createAccountDatabaseV1

What does the hosting_createAccountDatabaseV1 tool do? +

Creates a database with a database user and password for the specified account. The database name and user are automatically prefixed with the account username when needed. 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 hosting_createAccountDatabaseV1 accept? +

hosting_createAccountDatabaseV1 accepts 5 parameters: name, user, password, username, website_domain. Required: name, user, password, username, website_domain. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hosting_createAccountDatabaseV1? +

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

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

Can I rate-limit hosting_createAccountDatabaseV1? +

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

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

hosting_createAccountDatabaseV1 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger Api's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.