read_variable_at_step

Reads a named variable at a specific step from a BP5 file. All parameters are required.

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-variable-at-step.md

WHAT IT DOES

What read_variable_at_step does on CLIO Adios

AI agents call read_variable_at_step 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_variable_at_step is rated Low

This tool retrieves scientific data from BP5 checkpoint files without creating, modifying, deleting, or executing operations. It is a query operation with read-only semantics. The context of ADIOS2 (scientific data format) and sibling tools (analyze_*, aggregate_*) confirm this is part of a data analysis pipeline where this tool provides safe, non-destructive access to stored variables.

From the tool's definition Tool name 'read_variable_at_step' and description 'Reads a named variable at a specific step from a BP5 file' indicate data retrieval with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

read_variable_at_step Allowed

read_variable_at_step 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_variable_at_step": {}
  }
}

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_variable_at_step call is checked against it from then on.

FAQ

Questions about read_variable_at_step

What does the read_variable_at_step tool do? +

Reads a named variable at a specific step from a BP5 file. All parameters are required. 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_variable_at_step? +

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

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

Can I rate-limit read_variable_at_step? +

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

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

read_variable_at_step 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 →