Set a connection as the default.
AI agents use kusto_connection_set_default 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 modifies metadata/configuration (the default connection preference) but does not execute queries, access data, or produce destructive side effects. It is a reversible Write operation that updates internal state.
From the tool's definition Tool name 'kusto_connection_set_default' and description 'Set a connection as the default' indicate modification of configuration state. This changes which connection is used by default in subsequent operations.
Attacks that exploit this kind of access
Set a connection as the default. 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_set_default: 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_set_default 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_set_default 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_set_default. 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_set_default 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 →