AI agents invoke liara_stop_database to trigger actions in Liara MCP Server. 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.
Stopping a database is an execute operation that halts a critical service, not a destructive action (data remains), but it disrupts availability and affects system state irreversibly until the database is restarted. This has significant blast radius if triggered unintentionally by an AI agent, potentially causing service outages.
From the tool's definition 'Stop a database' - halts a running database service, which is an operational action that triggers external state changes on the Liara infrastructure.
Documented attack patterns abuse exactly the kind of access liara_stop_database 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_stop_database:
{
"version": "1",
"default": "deny",
"tools": {
"liara_stop_database": {
"limits": [
{
"counter": "liara_stop_database_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}liara_stop_database 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.
Free to start. No card required.
Stop a database. It is categorised as a Execute tool in the Liara MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Liara MCP Server MCP server in PolicyLayer and add a rule for liara_stop_database: 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_stop_database 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 liara_stop_database 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_stop_database. 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_stop_database 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.