Execute a Kusto script file containing multiple KQL statements. Useful for running saved queries or batch operations.
AI agents invoke kusto_script 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.
This tool executes arbitrary code (KQL scripts) whose effects depend entirely on the script contents. While it could be used for read operations, the capability to execute multiple statements means it could also perform writes, deletes, or other side effects. This makes it an Execute tool rather than a simple Read tool.
From the tool's definition Tool description states 'Execute a Kusto script file containing multiple KQL statements.' The verb 'Execute' combined with the ability to run 'multiple KQL statements' indicates code execution capability.
Attacks that exploit this kind of access
Execute a Kusto script file containing multiple KQL statements. Useful for running saved queries or batch operations. 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.
Register the Kusto MCP Server MCP server in PolicyLayer and add a rule for kusto_script: 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.
kusto_script is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the kusto_script 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.
Set action: deny in the PolicyLayer policy for kusto_script. 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.
kusto_script is provided by the Kusto MCP Server MCP server (yeshsurya/kusto-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →