AI agents use vibekit_enable_database to create or update resources in Vibekit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vibekit environment.
This tool provisions/enables a database resource for an application. It creates or activates a new managed Postgres database, which is a reversible write/configuration operation (it can be disabled or removed later). It does not delete data, execute arbitrary code, or move money, though it may have cost implications for users requiring add-ons.
From the tool's definition Enable a managed Postgres database for an app
Attacks that exploit this kind of access
Enable a managed Postgres database for an app. Free tier users need the database add-on. It is categorised as a Write tool in the Vibekit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vibekit MCP server in PolicyLayer and add a rule for vibekit_enable_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 Vibekit. Nothing to install.
vibekit_enable_database 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 vibekit_enable_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 vibekit_enable_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.
vibekit_enable_database 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →