This record as markdown: /tools/io-github-kivanccakmak-yaver/db-backup.md
What db_backup does on Yaver
AI agents call db_backup to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
db_url | string | — | Database URL (auto-detected from .env if omitted) |
Parameters from the server's own tool schema.
Why db_backup is rated Low
Database backup operations are fundamentally Read operations—they retrieve and duplicate database state without altering, deleting, or destroying data. While backups have operational importance, the tool itself performs no side effects on the live database. Severity is low because misuse (e.g., creating unwanted backups) causes resource consumption but no data loss or corruption.
From the tool's definition Tool name 'db_backup' and description 'Backup database (pg_dump / SQLite copy / mysqldump)' indicate read-only operations that extract and copy database contents without modifying the source.
Attacks that exploit this kind of access
The rule that runs db_backup 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_backup, this is the rule to start with:
db_backup is read-only, so it stays allowed. 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_backup call is checked against it from then on.
Questions about db_backup
Backup database (pg_dump / SQLite copy / mysqldump). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
db_backup accepts 1 parameter: db_url. 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_backup: 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_backup is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the db_backup 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_backup. 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_backup 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.
This server
Across the catalogue