duplicate_database · Fusebase MCP Server MCP: Risk & Policy

WHAT IT DOES

What duplicate_database does on Fusebase MCP Server

AI agents use duplicate_database to create or update resources in Fusebase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fusebase MCP Server environment.

WHY IT NEEDS A POLICY

Why duplicate_database needs a policy

This tool creates a new copy of an entire database structure and potentially its data. It is a Write operation (creates new data reversibly) rather than Destructive. However, severity is high because it duplicates entire databases including tables, views, relations, and data, which could result in significant unintended data duplication, storage consumption, and exposure of sensitive information if misused by an AI…

From the tool's definition Duplicate (copy) an entire database, including tables, views, relations, and optionally data. Returns the new database with its UUIDs.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

duplicate_database Rate-limited

duplicate_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "duplicate_database": {
      "limits": [
        {
          "counter": "duplicate_database_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Fusebase MCP Server, so you can run agents against it safely.

FAQ

Questions about duplicate_database

What does the duplicate_database tool do? +

Duplicate (copy) an entire database, including tables, views, relations, and optionally data. Returns the new database with its UUIDs. Discovered via captured API: POST /databases/copy-from/database. It is categorised as a Write tool in the Fusebase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on duplicate_database? +

Register the Fusebase MCP Server MCP server in PolicyLayer and add a rule for duplicate_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 Fusebase MCP Server. Nothing to install.

What risk level is duplicate_database? +

duplicate_database is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit duplicate_database? +

Yes. Add a rate_limit block to the duplicate_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.

How do I block duplicate_database completely? +

Set action: deny in the PolicyLayer policy for duplicate_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.

What MCP server provides duplicate_database? +

duplicate_database is provided by the Fusebase MCP Server MCP server (ryan-haver/fusebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.