module_list

List all currently loaded environment modules.

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/module-list.md

WHAT IT DOES

What module_list does on CLIO Adios

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

This tool performs a read-only inspection of the current environment module configuration. It has no side effects, does not modify data, execute external commands, or trigger operations. The blast radius of misuse is minimal—an AI agent could only learn what modules are loaded, which is non-sensitive operational information in a scientific computing context.

From the tool's definition Tool name 'module_list' and description 'List all currently loaded environment modules' indicate a query operation that retrieves and reports current system state without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

module_list Allowed

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

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

FAQ

Questions about module_list

What does the module_list tool do? +

List all currently loaded environment modules. 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 module_list? +

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

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

Can I rate-limit module_list? +

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

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

module_list 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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