This record as markdown: /tools/kiln/backup-database.md
What backup_database does on Kiln
AI agents call backup_database to retrieve information from Kiln without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why backup_database is rated Low
Backup operations typically read and copy data without modifying the original (Read category). However, the empty description significantly limits confidence. The tool could theoretically have side effects (e.g., triggering maintenance mode, locking resources, or modifying backup metadata), which might elevate it to Write. In a 3D printer context, backing up configuration is generally reversible and non-destructive.
From the tool's definition Tool name 'backup_database' suggests data retrieval/copying operation. Description is empty, providing no actionable detail about implementation, scope, or side effects.
Attacks that exploit this kind of access
The rule that runs backup_database safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kiln, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For backup_database, this is the rule to start with:
backup_database 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 Kiln, apply this rule, and every backup_database call is checked against it from then on.
Questions about backup_database
backup_database is a read tool on the Kiln MCP server. It is categorised as a Read tool in the Kiln MCP Server, which means it retrieves data without modifying state.
Register the Kiln MCP server in PolicyLayer and add a rule for backup_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 Kiln. Nothing to install.
backup_database 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 backup_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 backup_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.
backup_database is provided by the Kiln MCP server (codeofaxel/Kiln). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Kiln, and thousands of servers like it.
This server
Across the catalogue