List functions in the current database
AI agents call show-functions to retrieve information from Kusto without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a straightforward metadata query to enumerate available functions. It has no side effects, does not execute code, and does not modify any data. The blast radius of misuse is minimal—an attacker could only discover what functions exist in the database, which is informational only.
From the tool's definition Tool name 'show-functions' and description 'List functions in the current database' indicate a read-only operation that retrieves metadata without modifying or executing any code.
Documented attack patterns abuse exactly the kind of access show-functions 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 show-functions:
{
"version": "1",
"default": "deny",
"tools": {
"show-functions": {}
}
}show-functions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List functions in the current database. It is categorised as a Read tool in the Kusto MCP Server, which means it retrieves data without modifying state.
Register the Kusto MCP server in PolicyLayer and add a rule for show-functions: 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.
show-functions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the show-functions 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 show-functions. 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.
show-functions 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.