execute_karte_sql · Karte Datahub MCP: Risk & Policy

WHAT IT DOES

What execute_karte_sql does on Karte Datahub

AI agents invoke execute_karte_sql to trigger actions in Karte Datahub. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why execute_karte_sql needs a policy

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. SQL execution is categorized as Execute rather than Read because it can trigger arbitrary operations on the database whose effects depend on the SQL provided.

From the tool's definition Tool name 'execute_karte_sql' indicates SQL execution capability. Server description confirms it enables querying and analyzing KARTE event data 'via BigQuery.' Sibling tools (count_karte_events, describe_karte_events_schema, query_karte_events) show this is…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_karte_sql Rate-limited

execute_karte_sql stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_karte_sql": {
      "limits": [
        {
          "counter": "execute_karte_sql_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about execute_karte_sql

What does the execute_karte_sql tool do? +

execute_karte_sql. It is categorised as a Execute tool in the Karte Datahub MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_karte_sql? +

Register the Karte Datahub MCP server in PolicyLayer and add a rule for execute_karte_sql: 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 Karte Datahub. Nothing to install.

What risk level is execute_karte_sql? +

execute_karte_sql is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_karte_sql? +

Yes. Add a rate_limit block to the execute_karte_sql 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 execute_karte_sql completely? +

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

execute_karte_sql is provided by the Karte Datahub MCP server (yusukeyajima/karte-datahub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.