Retrieves the schema information for a specified table in the Azure Data Explorer database, including column names, data types, and other schema-related metadata.
AI agents call get_table_schema 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.
This is a pure metadata read operation that queries database schema details. It has no side effects, creates no resources, executes no code, and modifies nothing. The blast radius of misuse is minimal—an attacker could learn database structure but cannot access, modify, or delete data through this tool alone.
From the tool's definition Tool description states it 'Retrieves...schema information' and 'includes column names, data types, and other schema-related metadata.' The verb 'Retrieves' and the read-only nature of schema metadata inspection confirm no data modification, deletion, or code…
Documented attack patterns abuse exactly the kind of access get_table_schema 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 get_table_schema:
{
"version": "1",
"default": "deny",
"tools": {
"get_table_schema": {}
}
}get_table_schema 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 the schema information for a specified table in the Azure Data Explorer database, including column names, data types, and other schema-related metadata. 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 get_table_schema: 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.
get_table_schema 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 get_table_schema 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 get_table_schema. 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.
get_table_schema 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.