This record as markdown: /tools/io-github-portel-dev-ncp/backup-database.md
What backup_database does on Ncp
AI agents use backup_database to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why backup_database is rated Medium
Backup operations create new data artifacts (backup files) and are reversible write actions. While backups are protective in intent, they create/modify data on the system (write category). The severity is high because improper backup creation could lead to storage issues, resource exhaustion, or if the backup process interferes with database operations, could impact availability.
From the tool's definition Tool name 'backup_database' with description 'Create backup of MySQL database' indicates a data creation/write operation that generates a backup artifact.
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 Ncp, 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 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 Ncp, apply this rule, and every backup_database call is checked against it from then on.
Questions about backup_database
Create backup of MySQL database. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp 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 Ncp. Nothing to install.
backup_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 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 Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue