restore_backup

Restore knowledge base from a backup. WARNING: This will replace the current database. A safety backup is created automatically before restoration.

Server TDZ C64 Knowledge michaeltroelsen/tdz-c64-knowledge
Category Destructive
Risk class Critical
Parameters 00 required

What restore_backup does on TDZ C64 Knowledge

AI agents call restore_backup to permanently remove resources in TDZ C64 Knowledge — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why restore_backup needs a policy

Restoring a backup replaces the current database entirely. Even though a safety backup is created first, the act of overwriting all live data with a prior snapshot is effectively destructive and irreversible in terms of any changes made since the backup. The blast radius is critical — an AI agent misusing this tool could wipe out all current indexed documents and knowledge.

From the tool's definition 'WARNING: This will replace the current database' — explicitly overwrites the entire current knowledge base with backup data, an irreversible replacement of all live data

Questions about restore_backup

What does the restore_backup tool do? +

Restore knowledge base from a backup. WARNING: This will replace the current database. A safety backup is created automatically before restoration. It is categorised as a Destructive tool in the TDZ C64 Knowledge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on restore_backup? +

Register the TDZ C64 Knowledge MCP server in PolicyLayer and add a rule for restore_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 TDZ C64 Knowledge. Nothing to install.

What risk level is restore_backup? +

restore_backup is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit restore_backup? +

Yes. Add a rate_limit block to the restore_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.

How do I block restore_backup completely? +

Set action: deny in the PolicyLayer policy for restore_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.

What MCP server provides restore_backup? +

restore_backup is provided by the TDZ C64 Knowledge MCP server (michaeltroelsen/tdz-c64-knowledge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.