Restore database from backup
AI agents use restore_database to create or update resources in Follow Plan MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Follow Plan MCP Server environment.
The restore_database tool modifies data by replacing the current database with a backup version. This is categorized as Write rather than Destructive because: (1) the operation is theoretically reversible (the overwritten state could be backed up again), (2) data is not permanently deleted but replaced with a previous version, and (3) the tool provides recovery functionality.
From the tool's definition Tool name 'restore_database' with description 'Restore database from backup' indicates overwriting the current database state with backed-up data.
Attacks that exploit this kind of access
Restore database from backup. It is categorised as a Write tool in the Follow Plan MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Follow Plan MCP Server MCP server in PolicyLayer and add a rule for restore_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 Follow Plan MCP Server. Nothing to install.
restore_database is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the restore_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 restore_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.
restore_database is provided by the Follow Plan MCP Server MCP server (vibeclasses/follow-plan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →