Low Risk

get_table_details

Retrieves table details including TotalRowCount, HotExtentSize

How to control get_table_details ↓

AI agents call get_table_details 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.

Low Risk

This tool retrieves metadata and statistics about a table (row count, extent size) without creating, modifying, deleting, or executing any operations. It is purely informational and fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The 'get' verb and retrieval-focused description confirm this classification.

From the tool's definition Tool name 'get_table_details' and description 'Retrieves table details including TotalRowCount, HotExtentSize' indicate a read-only data query operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_table_details 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_details:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_table_details": {}
  }
}

get_table_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Adx — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_table_details tool do? +

Retrieves table details including TotalRowCount, HotExtentSize. It is categorised as a Read tool in the Adx MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_table_details? +

Register the Adx MCP server in PolicyLayer and add a rule for get_table_details: 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.

What risk level is get_table_details? +

get_table_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_table_details? +

Yes. Add a rate_limit block to the get_table_details 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.

How do I block get_table_details completely? +

Set action: deny in the PolicyLayer policy for get_table_details. 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.

What MCP server provides get_table_details? +

get_table_details 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.

Enforce policy on every Adx tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.