execute_query_internal_table · Kusto MCP Server MCP

WHAT IT DOES

What execute_query_internal_table does on Kusto MCP Server

AI agents invoke execute_query_internal_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_internal_table needs a policy

This tool enables execution of KQL queries, which are external operations triggered by user-supplied arguments (the query text). The blast radius is significant: a malicious or erroneous query could consume excessive compute resources, expose sensitive data at scale, or perform unintended analytical operations on an Azure Data Explorer cluster.

From the tool's definition The tool performs 'Execute a kql query' on internal tables or materialized views. KQL (Kusto Query Language) queries can include aggregations, transformations, and complex operations that go beyond simple data retrieval.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_query_internal_table Rate-limited

execute_query_internal_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_internal_table": {
      "limits": [
        {
          "counter": "execute_query_internal_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_internal_table

What does the execute_query_internal_table tool do? +

Execute a kql query to internal table or materialized view. 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_internal_table? +

Register the Kusto MCP Server MCP server in PolicyLayer and add a rule for execute_query_internal_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_internal_table? +

execute_query_internal_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_internal_table? +

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

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

execute_query_internal_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.