// SCAN REPORT

Tailpipe

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

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

Last updated: 12 Jun 2026

1 can modify or destroy data

9 read-only

10 tools total

Community server · catalogue entry verified 12/06/2026

How to control Tailpipe ↓

TOOL MAP

What Tailpipe exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Tailpipe tools

Execute · High tailpipe_connect This tool initializes a DuckDB database engine by executing an SQL init script.

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

POLICY

How to control Tailpipe

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

Cap read operations

{
  "tailpipe_partition_list": {
    "limits": [
      {
        "counter": "tailpipe_partition_list_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 Tailpipe — 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 TAILPIPE →

Free to start. No card required.

FULL CATALOGUE

All 10 Tailpipe tools

EXECUTE 1 tools

Execute tailpipe_connect Initialize DuckDB using a Tailpipe init SQL script, optionally specifying a new init script path.

READ 9 tools

Read tailpipe_partition_list List all Tailpipe partitions with their file counts and sizes. Read tailpipe_partition_show Get detailed information about a specific Tailpipe partition, including its configuration and statistics. Read tailpipe_plugin_list List all installed Tailpipe plugins with their versions and associated partitions. Read tailpipe_plugin_show Get detailed information about a specific Tailpipe plugin, including its configuration and dependencies. Read tailpipe_query Execute read-only SQL queries against cloud and security logs using DuckDB syntax. Results are returned in JSO Read tailpipe_source_list List all available Tailpipe data sources with their associated plugins. Read tailpipe_source_show Get detailed information about a specific Tailpipe data source, including its configuration and plugin details Read tailpipe_table_list List all available Tailpipe tables, including their schemas, descriptions, and column counts. Use tailpipe_tab Read tailpipe_table_show Get detailed information about a specific Tailpipe table, including its schema, column definitions, data types

FAQ

Questions about Tailpipe

Is the Tailpipe MCP server safe to use without restrictions? +

The Tailpipe server is primarily read-only with 9 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 Tailpipe MCP server expose? +

10 tools across 2 categories: Read, Write. 9 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Tailpipe? +

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

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

ENFORCE POLICY ON TAILPIPE →

Free to start. No card required.

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