google_cloud_run_query · VibeServe MCP: Risk & Policy

WHAT IT DOES

What google_cloud_run_query does on VibeServe

AI agents invoke google_cloud_run_query to trigger actions in VibeServe. 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.

WHY IT NEEDS A POLICY

Why google_cloud_run_query needs a policy

SQL query execution is a classic Execute category action: it triggers external operations (database queries) whose effects depend entirely on the SQL arguments provided. While the tool could theoretically support read-only queries (Read), it permits arbitrary SQL execution, which includes writes, transactions, and potentially destructive operations (DROP, DELETE, ALTER).

From the tool's definition Tool name and description state 'Run a Google Cloud SQL query' — this explicitly executes arbitrary SQL commands against a production database.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

google_cloud_run_query Rate-limited

google_cloud_run_query 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "google_cloud_run_query": {
      "limits": [
        {
          "counter": "google_cloud_run_query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches VibeServe, so you can run agents against it safely.

FAQ

Questions about google_cloud_run_query

What does the google_cloud_run_query tool do? +

Run a Google Cloud SQL query. It is categorised as a Execute tool in the VibeServe MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on google_cloud_run_query? +

Register the VibeServe MCP server in PolicyLayer and add a rule for google_cloud_run_query: 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 VibeServe. Nothing to install.

What risk level is google_cloud_run_query? +

google_cloud_run_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit google_cloud_run_query? +

Yes. Add a rate_limit block to the google_cloud_run_query 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.

How do I block google_cloud_run_query completely? +

Set action: deny in the PolicyLayer policy for google_cloud_run_query. 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.

What MCP server provides google_cloud_run_query? +

google_cloud_run_query is provided by the VibeServe MCP server (ncsound919/vibeserve). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.