Retrieves a list of all tables available in the configured Azure Data Explorer database, including their names, folders, and database associations.
AI agents call list_tables to retrieve information from Adx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a retrieval/query operation to discover available tables and their metadata. It has no side effects, makes no modifications, executes no code, and poses minimal risk even if misused by an AI agent—the worst outcome would be information disclosure about database schema structure.
From the tool's definition Tool description states it 'Retrieves a list of all tables available' in the Azure Data Explorer database. This is a read-only operation that queries metadata without modifying, executing, or deleting any data.
Documented attack patterns abuse exactly the kind of access list_tables gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Adx, and nothing reaches the server without passing your rules. This is the rule we recommend for list_tables:
{
"version": "1",
"default": "deny",
"tools": {
"list_tables": {}
}
}list_tables 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.
Retrieves a list of all tables available in the configured Azure Data Explorer database, including their names, folders, and database associations. It is categorised as a Read tool in the Adx MCP Server, which means it retrieves data without modifying state.
Register the Adx MCP server in PolicyLayer and add a rule for list_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 Adx. Nothing to install.
list_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_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_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_tables is provided by the Adx MCP server (pab1it0/adx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Adx tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 Adx tools catalogued and risk-classified — across an index of 42,500+ MCP servers.