Get detailed information about a table including columns, types, and sample data
AI agents call analyze_table to retrieve information from MCP Data Visualization Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs introspection on database tables to retrieve schema information (columns, types) and sample data. It is purely informational with no side effects—it does not create, modify, delete, or execute operations. The action is a read-only query operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'analyze_table' and description 'Get detailed information about a table including columns, types, and sample data' indicate retrieval of metadata and sample records with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access analyze_table gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Data Visualization Server, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_table:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_table": {}
}
} analyze_table 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.
Get detailed information about a table including columns, types, and sample data. It is categorised as a Read tool in the MCP Data Visualization Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Data Visualization Server MCP server in PolicyLayer and add a rule for analyze_table: 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 MCP Data Visualization Server. Nothing to install.
analyze_table 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 analyze_table 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 analyze_table. 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.
analyze_table is provided by the MCP Data Visualization Server MCP server (xoniks/mcp-visualization-duckdb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Data Visualization Server, 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.
28 MCP Data Visualization Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.