module_unload

Unload one or more currently loaded modules from the environment.

SERVERCLIO Adios SOURCEpypi:clio-kit

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-iowarp-adios-mcp/module-unload.md

WHAT IT DOES

What module_unload does on CLIO Adios

AI agents invoke module_unload to trigger actions in CLIO Adios. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why module_unload is rated High

Unloading environment modules changes the active software environment, which can break running processes, alter PATH/library availability, and affect subsequent tool executions. This is an environmental execution action with potentially broad side effects on the compute environment, but it is technically reversible (modules can be reloaded), so it falls under Execute rather than Destructive.

From the tool's definition 'Unload one or more currently loaded modules from the environment' — modifies the runtime environment by removing loaded modules

Attacks that exploit this kind of access

RECOMMENDED RULE

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

module_unload Rate-limited

module_unload stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "module_unload": {
      "limits": [
        {
          "counter": "module_unload_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about module_unload

What does the module_unload tool do? +

Unload one or more currently loaded modules from the environment. It is categorised as a Execute tool in the CLIO Adios MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on module_unload? +

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

module_unload is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit module_unload? +

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

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

module_unload 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 → High-risk tools on this server →

Across the catalogue

intercept_module_function on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →