AI agents use liara_restore_backup to create or update resources in Liara MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Liara MCP Server environment.
Restoring a backup writes data to an existing database, potentially overwriting current data. While reversible (the current state could be backed up first), this is a significant modification that could disrupt services and cause data loss if misused.
From the tool's definition Tool name 'liara_restore_backup' and description 'Restore a database from a backup' indicate the tool modifies an existing database by overwriting it with backup data.
Documented attack patterns abuse exactly the kind of access liara_restore_backup gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Liara MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for liara_restore_backup:
{
"version": "1",
"default": "deny",
"tools": {
"liara_restore_backup": {
"limits": [
{
"counter": "liara_restore_backup_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}liara_restore_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 database from a backup. It is categorised as a Write tool in the Liara MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Liara MCP Server MCP server in PolicyLayer and add a rule for liara_restore_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 Liara MCP Server. Nothing to install.
liara_restore_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 liara_restore_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 liara_restore_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.
liara_restore_backup is provided by the Liara MCP Server MCP server (razavioo/liara-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Liara 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.
108 Liara MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.