Add or update a named connection configuration for Azure Data Explorer.
AI agents use kusto_connection_add to create or update resources in Kusto MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kusto MCP Server environment.
This tool creates or modifies connection metadata (credentials, cluster endpoints, etc.) without deleting data or executing queries. It is Write-category because configuration changes are reversible—a connection can be updated or removed.
From the tool's definition Tool description states 'Add or update a named connection configuration' — these are reversible modifications to connection settings stored in the system.
Attacks that exploit this kind of access
Add or update a named connection configuration for Azure Data Explorer. It is categorised as a Write tool in the Kusto MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kusto MCP Server MCP server in PolicyLayer and add a rule for kusto_connection_add: 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_connection_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the kusto_connection_add 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_connection_add. 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_connection_add 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 →