get_node_info

Get information about Slurm cluster nodes and their resources.

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/get-node-info.md

WHAT IT DOES

What get_node_info does on CLIO Adios

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

This tool retrieves metadata about cluster nodes (CPU count, memory, state, etc.) without side effects. It is a read-only query operation analogous to 'list' or 'get'. No data is modified, code is executed, or resources are allocated by this tool alone. Severity is low because misuse would only expose non-sensitive infrastructure metadata.

From the tool's definition Tool name is 'get_node_info' and description states 'Get information about Slurm cluster nodes and their resources' — purely informational retrieval with no modification, execution, or deletion capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_node_info Allowed

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

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

FAQ

Questions about get_node_info

What does the get_node_info tool do? +

Get information about Slurm cluster nodes and their resources. 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 get_node_info? +

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

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

Can I rate-limit get_node_info? +

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

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

get_node_info 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

get_team_info on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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