// SCAN REPORT

Karte Datahub

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 Karte Datahub ↓

TOOL MAP

What Karte Datahub 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 Karte Datahub tools

Execute · High execute_karte_sql While the tool description is empty, the name 'execute_karte_sql' combined with the server's BigQuery integration and data analysis purpose clearly indicates this tool executes SQL queries.

1 of Karte Datahub'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 Karte Datahub

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

Cap read operations

{
  "count_karte_events": {
    "limits": [
      {
        "counter": "count_karte_events_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 Karte Datahub — 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 KARTE DATAHUB →

Instant setup, no code required.

FULL CATALOGUE

All 4 Karte Datahub tools

EXECUTE 1 tools

Execute execute_karte_sql execute_karte_sql

READ 3 tools

Read count_karte_events KARTEイベントの件数を取得する。 Read describe_karte_events_schema KARTEイベントテーブルのスキーマを取得する。 Read query_karte_events query_karte_events

EXPLORE

Related servers

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

FAQ

Questions about Karte Datahub

Is the Karte Datahub MCP server safe to use without restrictions? +

The Karte Datahub 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 Karte Datahub MCP server expose? +

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

How do I enforce a policy on Karte Datahub? +

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

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

ENFORCE POLICY ON KARTE DATAHUB →

Instant setup, no code required.

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