execute_query_external_table · Kusto MCP Server MCP

WHAT IT DOES

What execute_query_external_table does on Kusto MCP Server

AI agents invoke execute_query_external_table to trigger actions in Kusto MCP Server. 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_query_external_table needs a policy

This tool executes arbitrary KQL queries against external tables in Azure Data Explorer. While the description doesn't explicitly mention write or delete capabilities, KQL supports DML operations (update, delete), and execution of untrusted queries could modify or exfiltrate data. External tables may span multiple data sources, amplifying risk.

From the tool's definition Tool name includes 'execute' and description states 'Execute a kql query'. KQL (Kusto Query Language) queries can include data modification operations (update, delete) and external table access may have broader blast radius than internal tables.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_query_external_table Rate-limited

execute_query_external_table 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_query_external_table": {
      "limits": [
        {
          "counter": "execute_query_external_table_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 Kusto MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_query_external_table

What does the execute_query_external_table tool do? +

Execute a kql query to external table. It is categorised as a Execute tool in the Kusto MCP Server 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_query_external_table? +

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

What risk level is execute_query_external_table? +

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

Can I rate-limit execute_query_external_table? +

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

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

execute_query_external_table is provided by the Kusto MCP Server MCP server (zzzhdw/mcp-server-kusto). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.