Restore a database to a specific point in time or from a snapshot. This operation allows you to recover a database to a previous state. Key Features: - Restore to a specific timestamp or snapshot. - Supports both full and partial restores. Use Cases: - Recover from accidental data loss. - Restore...
AI agents use restore_database to create or update resources in NDB MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NDB MCP Server environment.
Restore operations are Write category actions because they modify and overwrite existing database state reversibly—the previous state is not destroyed permanently, and the operation can be undone by restoring again or rolling forward. However, severity is high because careless restoration could overwrite recent legitimate data, causing significant business impact.
From the tool's definition Tool description states 'Restore a database to a specific point in time or from a snapshot' and 'recover a database to a previous state'. Accepts parameters like 'database ID' and 'restore parameters (timestamp or snapshot ID)'.
Attacks that exploit this kind of access
Restore a database to a specific point in time or from a snapshot. This operation allows you to recover a database to a previous state. Key Features: - Restore to a specific timestamp or snapshot. - Supports both full and partial restores. Use Cases: - Recover from accidental data loss. - Restore a database to a known good state for testing or troubleshooting. Instructions: - Provide the database ID and the restore parameters (timestamp or snapshot ID). - userPitrTimestamp must be using the following format: YYYY-MM-DD HH:mm:ss. It is using GMT so convert it to your local timezone before using it. - Ensure the database is in a state that allows restoration. - Validate the restore operation using the returned status. - If an error occur, stop and wait for instructions. It is categorised as a Write tool in the NDB MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NDB 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 NDB 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 NDB MCP Server MCP server (rouxton/ndb-mcp-server). 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 →