This record as markdown: /tools/hostinger-mcp/agency-db-create-user.md
What agency_db_create_user does on Hostinger
AI agents use agency_db_create_user to create or update resources in Hostinger, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger environment.
Why agency_db_create_user is rated Medium
This tool creates a new database user, which is a reversible write operation. It modifies the database user population but does not delete, execute code, or transfer funds. However, it carries medium severity because improper creation of database users could grant unintended access to sensitive data or systems, posing a moderate security risk if misused by an agent.
From the tool's definition Tool name is 'agency_db_create_user' and description states 'Create a database user.' The verb 'Create' indicates a write operation that creates a new resource (database user account).
Attacks that exploit this kind of access
The rule that runs agency_db_create_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_create_user, this is the rule to start with:
agency_db_create_user 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, apply this rule, and every agency_db_create_user call is checked against it from then on.
Questions about agency_db_create_user
Create a database user. It is categorised as a Write tool in the Hostinger MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hostinger MCP server in PolicyLayer and add a rule for agency_db_create_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.
agency_db_create_user 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_db_create_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.
Set action: deny in the PolicyLayer policy for agency_db_create_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.
agency_db_create_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.
More on Hostinger, and thousands of servers like it.
This server
Across the catalogue