Restore a MySQL database from a backup file
AI agents use restore_database_backup to create or update resources in cPanel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your cPanel MCP Server environment.
Restoring a database from backup is a reversible write operation—it overwrites current database contents with historical data, but the action can be undone by creating a new backup or restoring to a different point in time. It is not Destructive because the original data is not permanently lost (backups exist), and the operation is theoretically reversible.
From the tool's definition Tool name 'restore_database_backup' and description 'Restore a MySQL database from a backup file' indicate the tool modifies database state by restoring data from a backup.
Documented attack patterns abuse exactly the kind of access restore_database_backup gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and cPanel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for restore_database_backup:
{
"version": "1",
"default": "deny",
"tools": {
"restore_database_backup": {
"limits": [
{
"counter": "restore_database_backup_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} restore_database_backup 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.
Free to start. No card required.
Restore a MySQL database from a backup file. It is categorised as a Write tool in the cPanel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the cPanel MCP Server MCP server in PolicyLayer and add a rule for restore_database_backup: 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 cPanel MCP Server. Nothing to install.
restore_database_backup 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 restore_database_backup 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 restore_database_backup. 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.
restore_database_backup is provided by the cPanel MCP Server MCP server (0xhayd3n/cpanel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from cPanel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
164 cPanel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.