restore_db
A write tool on the Metis Public Health MCP server.
This record as markdown: /tools/sveritg-metis-ph/restore-db.md
What restore_db does on Metis Public Health
AI agents use restore_db to create or update resources in Metis Public Health, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metis Public Health environment.
Why restore_db is rated Medium
A database restore operation modifies the current state of data by replacing it with a prior version. While it does not permanently delete original data (the backup remains), it does irreversibly alter the current database state and could overwrite recent changes.
From the tool's definition Tool name 'restore_db' indicates restoration/recovery of a database, which involves modifying or overwriting the current database state with a previous snapshot or backup.
Attacks that exploit this kind of access
The rule that runs restore_db safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Metis Public Health, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For restore_db, this is the rule to start with:
restore_db stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Metis Public Health, apply this rule, and every restore_db call is checked against it from then on.
Questions about restore_db
restore_db is a write tool on the Metis Public Health MCP server. It is categorised as a Write tool in the Metis Public Health MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for restore_db: 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 Metis Public Health. Nothing to install.
restore_db 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_db 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_db. 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_db is provided by the Metis Public Health MCP server (sveritg/metis_ph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Metis Public Health, and thousands of servers like it.
This server
Across the catalogue