// SCAN REPORT

Duckdb Iceberg

4 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

1 can modify or destroy data

3 read-only

4 tools total

Community server · catalogue entry verified 03/07/2026

How to control Duckdb Iceberg ↓

TOOL MAP

What Duckdb Iceberg exposes to your agents

Read (3) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Duckdb Iceberg tools

Execute · High query_lakehouse The tool executes arbitrary SQL queries against S3-backed Iceberg tables via DuckDB.

1 of Duckdb Iceberg's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Duckdb Iceberg

PolicyLayer is an MCP gateway — it sits between your AI agents and Duckdb Iceberg, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "describe_table": {
    "limits": [
      {
        "counter": "describe_table_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Duckdb Iceberg — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON DUCKDB ICEBERG →

Instant setup, no code required.

FULL CATALOGUE

All 4 Duckdb Iceberg tools

EXECUTE 1 tools

Execute query_lakehouse Execute a SQL query. Use read_parquet() or iceberg_scan() for S3 paths,

READ 3 tools

Read describe_table Describe a table's schema. Use 'database.table' format for Glue. Read glue_table glue_table Read list_tables List available tables. Optionally filter by database name.

FAQ

Questions about Duckdb Iceberg

Is the Duckdb Iceberg MCP server safe to use without restrictions? +

The Duckdb Iceberg server is primarily read-only with 3 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Duckdb Iceberg MCP server expose? +

4 tools across 1 categories: Read. 3 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Duckdb Iceberg? +

Register the Duckdb Iceberg MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Duckdb Iceberg tool call.

Deterministic rules across all 4 Duckdb Iceberg tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON DUCKDB ICEBERG →

Instant setup, no code required.

4 Duckdb Iceberg tools catalogued and risk-classified — across an index of 43,000+ MCP servers.