Creates connection to an ADX cluster
AI agents invoke initialize-connection to trigger actions in Kusto. 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.
While the tool itself does not query or delete data, initializing a connection to a database cluster is an Execute action because it triggers an external operation (ADX session establishment) whose effects depend on the connection parameters provided. However, severity is medium rather than high because the connection itself does not directly read, modify, or destroy data—subsequent queries would do that.
From the tool's definition Tool creates a connection to an Azure Data Explorer (ADX) cluster. Connecting to an external service establishes a session that triggers external operations and state changes on the ADX infrastructure, which qualifies as execution of an external operation.
Documented attack patterns abuse exactly the kind of access initialize-connection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kusto, and nothing reaches the server without passing your rules. This is the rule we recommend for initialize-connection:
{
"version": "1",
"default": "deny",
"tools": {
"initialize-connection": {
"limits": [
{
"counter": "initialize-connection_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}initialize-connection 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.
Free to start. No card required.
Creates connection to an ADX cluster. It is categorised as a Execute tool in the Kusto MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kusto MCP server in PolicyLayer and add a rule for initialize-connection: 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. Nothing to install.
initialize-connection 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 initialize-connection 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 initialize-connection. 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.
initialize-connection is provided by the Kusto MCP server (johnib/kusto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kusto, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Kusto tools catalogued and risk-classified — across an index of 43,000+ MCP servers.