read_slice_tool

Read a row slice from a Parquet file with optional column projection and filtering.

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/read-slice-tool.md

WHAT IT DOES

What read_slice_tool does on CLIO Adios

AI agents call read_slice_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 read_slice_tool is rated Low

This tool performs a query operation on scientific data files (Parquet format) with optional filtering and column projection. It retrieves a subset of rows without creating, modifying, deleting, or executing arbitrary code. The operation is read-only with no side effects, matching the Read category.

From the tool's definition Tool name 'read_slice_tool' and description 'Read a row slice from a Parquet file with optional column projection and filtering' explicitly indicate data retrieval with no modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs read_slice_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 read_slice_tool, this is the rule to start with:

read_slice_tool Allowed

read_slice_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": {
    "read_slice_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 read_slice_tool call is checked against it from then on.

FAQ

Questions about read_slice_tool

What does the read_slice_tool tool do? +

Read a row slice from a Parquet file with optional column projection and filtering. 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 read_slice_tool? +

Register the CLIO Adios MCP server in PolicyLayer and add a rule for read_slice_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 read_slice_tool? +

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

Can I rate-limit read_slice_tool? +

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

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

read_slice_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

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

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