This record as markdown: /tools/io-github-kivanccakmak-yaver/db-studio.md
What db_studio does on Yaver
AI agents invoke db_studio to trigger actions in Yaver. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
port | integer | — | Port for studio UI |
Parameters from the server's own tool schema.
Why db_studio is rated High
The tool opens/launches an external GUI application (Drizzle Studio or Prisma Studio). This triggers an external operation — starting a process/server — rather than simply reading data or writing records. Since the GUI itself can perform reads, writes, and potentially destructive operations, the act of launching it is best classified as Execute.
From the tool's definition Open database GUI (Drizzle Studio or Prisma Studio)
Attacks that exploit this kind of access
The rule that runs db_studio safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For db_studio, this is the rule to start with:
db_studio 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every db_studio call is checked against it from then on.
Questions about db_studio
Open database GUI (Drizzle Studio or Prisma Studio). It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
db_studio accepts 1 parameter: port. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for db_studio: 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 Yaver. Nothing to install.
db_studio 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 db_studio 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 db_studio. 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.
db_studio is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue