// SCAN REPORT

Dune

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

1 destructive tool with no built-in limits. Policy required.

Last updated: 29 Jun 2026

4 can modify or destroy data

13 read-only

17 tools total

Community server · catalogue entry verified 29/06/2026

How to control Dune ↓

TOOL MAP

What Dune exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Dune tools

Destructive · High archive_query Archiving or deleting a query permanently removes it from Dune Analytics. Execute · High execute_query Although the tool executes a stored query rather than arbitrary code, it still qualifies as Execute because it triggers external operations on a third-party analytics platform whose outcomes depend on the query content. Write · Medium create_query This tool creates and stores a new query resource in Dune Analytics. Write · Medium update_query This tool modifies query configuration (SQL and description) reversibly without deleting or executing queries.

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

POLICY

How to control Dune

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

Deny destructive operations

{
  "archive_query": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "create_query": {
    "limits": [
      {
        "counter": "create_query_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "analyze_query_error": {
    "limits": [
      {
        "counter": "analyze_query_error_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 Dune — 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 DUNE →

Instant setup, no code required.

FULL CATALOGUE

All 17 Dune tools

DESTRUCTIVE 1 tools

Destructive archive_query Archive/Delete a query. (Requires Paid Plan)

EXECUTE 1 tools

Execute execute_query Execute a query by ID. Returns Job ID.

WRITE 2 tools

Write create_query Save a new query to Dune. Returns Query ID. (Requires Paid Plan) Write update_query Update SQL/description of an existing query. (Requires Paid Plan)

READ 13 tools

Read analyze_query_error Analyze failed queries and suggest fixes (e.g. for 'Column not found'). Read analyze_results Detect outliers (Z-score > 3) and trends in query results. Read export_results_to_csv Download full query results to local CSV. Read get_account_status Check remaining credits and budget limits. Read get_job_results_summary Get result preview (5 rows) and stats. Read get_job_status Check query execution status. Polls for 30s. Read get_query_details Get SQL and parameters for a query ID. Read get_session_budget Check remaining queries/credits for this session. Read get_spellbook_file_content Fetch raw content of a Spellbook file from GitHub. Read get_table_schema Get columns for a table. Costs Credits (runs SELECT LIMIT 0). Read list_user_queries List queries by user handle. Read search_public_queries Search public queries by keyword. Use this to discover table names from existing SQL. Read search_spellbook Search GitHub Spellbook for official tables (.sql/.yml). Zero-credit schema discovery.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Dune

Can an AI agent delete data through the Dune MCP server? +

Yes. The Dune server exposes 1 destructive tools including archive_query. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Dune? +

The Dune server has 2 write tools including create_query, update_query. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Dune.

How many tools does the Dune MCP server expose? +

17 tools across 3 categories: Execute, Read, Write. 13 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Dune? +

Register the Dune 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 Dune tool call.

Deterministic rules across all 17 Dune tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON DUNE →

Instant setup, no code required.

17 Dune tools catalogued and risk-classified — across an index of 43,000+ MCP servers.