This record as markdown: /tools/io-github-kivanccakmak-yaver/db-reset.md
What db_reset does on Yaver
AI agents call db_reset to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
force | boolean | — | Confirm destructive reset |
Parameters from the server's own tool schema.
Why db_reset is rated Critical
This tool permanently deletes all database tables and cannot be undone. Even though it re-migrates and re-seeds afterward, the original data is irretrievably lost. This is a classic Destructive action with critical blast radius: an AI agent calling this without intent could destroy the entire local development database and all its contents.
From the tool's definition Tool description explicitly states "Drop all tables, re-migrate, and re-seed" — dropping tables is irreversible data destruction. The requirement for force=true confirms intentional destructive design.
Attacks that exploit this kind of access
The rule that runs db_reset 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_reset, this is the rule to start with:
db_reset is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every db_reset call is checked against it from then on.
Questions about db_reset
Drop all tables, re-migrate, and re-seed. Requires force=true. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
db_reset accepts 1 parameter: force. 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_reset: 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_reset is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the db_reset 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_reset. 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_reset 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