Low Risk

get_column_statistics

Get detailed statistics for a specific column.

How to control get_column_statistics ↓

What get_column_statistics does on CSV Editor

AI agents call get_column_statistics to retrieve information from CSV Editor 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_statistics needs a policy

This tool retrieves and analyzes existing data to produce summary statistics (mean, median, standard deviation, etc.). It has no side effects—it does not create, modify, delete, or execute operations. It is a pure read operation consistent with data analysis and reporting functions.

From the tool's definition Tool name 'get_column_statistics' and description 'Get detailed statistics for a specific column' indicate a retrieval operation that computes and returns aggregate metrics without modifying, deleting, or executing external code.

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

How to control get_column_statistics

PolicyLayer is an MCP gateway — it sits between your AI agents and CSV Editor, and nothing reaches the server without passing your rules. This is the rule we recommend for get_column_statistics:

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

get_column_statistics 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 CSV Editor — 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_statistics

What does the get_column_statistics tool do? +

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

How do I enforce a policy on get_column_statistics? +

Register the CSV Editor MCP server in PolicyLayer and add a rule for get_column_statistics: 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 CSV Editor. Nothing to install.

What risk level is get_column_statistics? +

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

Can I rate-limit get_column_statistics? +

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

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

get_column_statistics is provided by the CSV Editor MCP server (santoshray02/csv-editor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CSV Editor tool call.

Start from CSV Editor, 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.

39 CSV Editor 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.