Launch a new Serverless DB instance in SkySQL
AI agents invoke launch_serverless_db to trigger actions in Skysql. 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.
While this creates a new resource (which could be classified as Write), the nature of launching a database instance in a cloud provider context constitutes executing a provisioning workflow with infrastructure-level consequences. It goes beyond simple data creation and involves external system operations.
From the tool's definition 'Launch a new Serverless DB instance' triggers creation and provisioning of cloud infrastructure resources, with effects that depend on configuration parameters (instance size, region, etc.).
Documented attack patterns abuse exactly the kind of access launch_serverless_db gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Skysql, and nothing reaches the server without passing your rules. This is the rule we recommend for launch_serverless_db:
{
"version": "1",
"default": "deny",
"tools": {
"launch_serverless_db": {
"limits": [
{
"counter": "launch_serverless_db_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}launch_serverless_db 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.
Launch a new Serverless DB instance in SkySQL. It is categorised as a Execute tool in the Skysql MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Skysql MCP server in PolicyLayer and add a rule for launch_serverless_db: 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 Skysql. Nothing to install.
launch_serverless_db 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 launch_serverless_db 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 launch_serverless_db. 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.
launch_serverless_db is provided by the Skysql MCP server (skysqlinc/skysql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Skysql, 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.
8 Skysql tools catalogued and risk-classified — across an index of 43,000+ MCP servers.