aggregate_column_tool

Compute aggregate statistics (min, max, mean, etc.) on a Parquet column.

SERVERCLIO Adios SOURCEpypi:clio-kit

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-iowarp-adios-mcp/aggregate-column-tool.md

WHAT IT DOES

What aggregate_column_tool does on CLIO Adios

AI agents call aggregate_column_tool to retrieve information from CLIO Adios without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why aggregate_column_tool is rated Low

This tool retrieves and analyzes existing data from a Parquet column to produce statistical summaries. It has no side effects—it does not create, modify, delete, or execute code. The operation is purely computational analysis of data that already exists, which is characteristic of Read-category tools.

From the tool's definition Tool description states 'Compute aggregate statistics (min, max, mean, etc.) on a Parquet column.' The verb 'compute' combined with 'aggregate statistics' indicates read-only querying of data without modification, deletion, or execution of arbitrary code.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs aggregate_column_tool safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CLIO Adios, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For aggregate_column_tool, this is the rule to start with:

aggregate_column_tool Allowed

aggregate_column_tool is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "aggregate_column_tool": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CLIO Adios, apply this rule, and every aggregate_column_tool call is checked against it from then on.

FAQ

Questions about aggregate_column_tool

What does the aggregate_column_tool tool do? +

Compute aggregate statistics (min, max, mean, etc.) on a Parquet column. It is categorised as a Read tool in the CLIO Adios MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on aggregate_column_tool? +

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

What risk level is aggregate_column_tool? +

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

Can I rate-limit aggregate_column_tool? +

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

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

aggregate_column_tool is provided by the CLIO Adios MCP server (pypi:clio-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CLIO Adios, and thousands of servers like it.

This server

All 204 CLIO Adios tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →