List all external tables in the database
AI agents call list_external_tables to retrieve information from Kusto MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about external tables without side effects. It performs a query operation (list/enumerate) that does not create, modify, delete, or execute any code. The blast radius of misuse is minimal — an agent might discover table names and schemas but cannot alter data or trigger external operations. Classified as Read with low severity.
From the tool's definition Tool name is 'list_external_tables' and description states 'List all external tables in the database' — a purely retrieval operation with no modification, deletion, or code execution.
Attacks that exploit this kind of access
List all external tables in the database. It is categorised as a Read tool in the Kusto MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kusto MCP Server MCP server in PolicyLayer and add a rule for list_external_tables: 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.
list_external_tables 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 list_external_tables 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 list_external_tables. 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.
list_external_tables is provided by the Kusto MCP Server MCP server (zzzhdw/mcp-server-kusto). 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 →