Low Risk

get_column_stats

Get detailed statistics for a specific column

How to control get_column_stats ↓

What get_column_stats does on MCP Data Visualization Server

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

Low Risk

Why get_column_stats needs a policy

This tool retrieves statistical summaries (mean, median, distribution, etc.) from a column in a database. It performs read-only operations—no data is created, modified, deleted, or executed as code. The blast radius is minimal: misuse would only expose data insights the user already has access to view. This is a standard analytical query operation.

From the tool's definition Tool name 'get_column_stats' and description 'Get detailed statistics for a specific column' indicate data retrieval and analysis operations.

Documented attack patterns abuse exactly the kind of access get_column_stats gives an agent:

How to control get_column_stats

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 get_column_stats:

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

get_column_stats 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 MCP Data Visualization Server — 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.

Related tools and policies

Go deeper

Questions about get_column_stats

What does the get_column_stats tool do? +

Get detailed statistics for a specific column. It is categorised as a Read tool in the MCP Data Visualization Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_column_stats? +

Register the MCP Data Visualization Server MCP server in PolicyLayer and add a rule for get_column_stats: 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.

What risk level is get_column_stats? +

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

Can I rate-limit get_column_stats? +

Yes. Add a rate_limit block to the get_column_stats 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_column_stats completely? +

Set action: deny in the PolicyLayer policy for get_column_stats. 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_column_stats? +

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

Enforce policy on every MCP Data Visualization Server tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.