This record as markdown: /tools/io-github-kivanccakmak-yaver/backend-backup.md
What backend_backup does on Yaver
AI agents call backend_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 |
|---|---|---|---|
output | string | — | Output path |
Parameters from the server's own tool schema.
Why backend_backup is rated Low
A backup operation reads/copies existing data to a safe location. It does not delete or modify source data, so it is not Destructive. However, it could Write a backup artifact to storage, making Write plausible. Since the primary action is copying/snapshotting data without modifying originals, Read is the most fitting category, though Write is a close second.
From the tool's definition 'Backup PocketBase data' — creates a backup copy of data
Attacks that exploit this kind of access
The rule that runs backend_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 backend_backup, this is the rule to start with:
backend_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 backend_backup call is checked against it from then on.
Questions about backend_backup
Backup PocketBase data. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
backend_backup accepts 1 parameter: output. 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 backend_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.
backend_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 backend_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 backend_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.
backend_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