AI agents use backup-database to create or update resources in MCP Firebird — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Firebird environment.
Creating a backup is a Write operation — it produces a new file/artifact but does not delete or overwrite existing data, and is reversible in the sense that the backup can be deleted. It is not Destructive, Execute (no arbitrary code), or Financial. Severity is medium because a misused backup could exfiltrate sensitive database contents or consume significant storage/resources.
From the tool's definition Creates a backup of the Firebird database
Documented attack patterns abuse exactly the kind of access backup-database gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Firebird, and nothing reaches the server without passing your rules. This is the rule we recommend for backup-database:
{
"version": "1",
"default": "deny",
"tools": {
"backup-database": {
"limits": [
{
"counter": "backup-database_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Creates a backup of the Firebird database. It is categorised as a Write tool in the MCP Firebird MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Firebird 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 MCP Firebird. 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 MCP Firebird MCP server (purodelphi/mcpfirebird). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 22 MCP Firebird tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
22 MCP Firebird tools catalogued and risk-classified — across an index of 42,500+ MCP servers.