vibekit_database_query · Vibekit MCP: Risk & Policy

WHAT IT DOES

What vibekit_database_query does on Vibekit

AI agents invoke vibekit_database_query to trigger actions in Vibekit. 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 vibekit_database_query needs a policy

This tool executes arbitrary SQL queries against a database. While named 'query', it can run any SQL including destructive DDL/DML (DROP, DELETE, TRUNCATE). The most severe applicable category is Execute (potentially Destructive depending on what SQL is submitted). Since the tool itself doesn't restrict to read-only queries, an AI agent could issue irreversible destructive commands.

From the tool's definition 'Run a SQL query against an app' — executes arbitrary SQL, which can include SELECT, INSERT, UPDATE, DELETE, or DROP statements

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vibekit_database_query Rate-limited

vibekit_database_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": {
    "vibekit_database_query": {
      "limits": [
        {
          "counter": "vibekit_database_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 Vibekit, so you can run agents against it safely.

FAQ

Questions about vibekit_database_query

What does the vibekit_database_query tool do? +

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

How do I enforce a policy on vibekit_database_query? +

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

What risk level is vibekit_database_query? +

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

Can I rate-limit vibekit_database_query? +

Yes. Add a rate_limit block to the vibekit_database_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 vibekit_database_query completely? +

Set action: deny in the PolicyLayer policy for vibekit_database_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 vibekit_database_query? +

vibekit_database_query is provided by the Vibekit MCP server (vibekit-apps/vibekit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.