hosting_repairDatabaseV1
Repairs corrupted database tables asynchronously. Use when database errors, crashes, or corruption are reported. The database name must be the full name returned by the list databases endpoint.
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/hosting-repairdatabasev1.md
What hosting_repairDatabaseV1 does on Hostinger Api
AI agents invoke hosting_repairDatabaseV1 to trigger actions in Hostinger Api. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Full database name as returned by the list databases endpoint. |
username | string | Yes | username parameter |
Parameters from the server's own tool schema.
Why hosting_repairDatabaseV1 is rated High
This tool executes a database repair operation asynchronously on remote infrastructure. While it is intended to fix corruption rather than delete data, it triggers an external operation (MySQL REPAIR TABLE or equivalent) that modifies database internals and could have unintended side effects on table data and structure.
From the tool's definition Repairs corrupted database tables asynchronously
Attacks that exploit this kind of access
The rule that runs hosting_repairDatabaseV1 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 hosting_repairDatabaseV1, this is the rule to start with:
hosting_repairDatabaseV1 stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 hosting_repairDatabaseV1 call is checked against it from then on.
Questions about hosting_repairDatabaseV1
Repairs corrupted database tables asynchronously. Use when database errors, crashes, or corruption are reported. The database name must be the full name returned by the list databases endpoint. It is categorised as a Execute tool in the Hostinger Api MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
hosting_repairDatabaseV1 accepts 2 parameters: name, username. Required: name, username. 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 hosting_repairDatabaseV1: 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.
hosting_repairDatabaseV1 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the hosting_repairDatabaseV1 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 hosting_repairDatabaseV1. 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.
hosting_repairDatabaseV1 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