get_job_output

Retrieve stdout or stderr output from a Slurm job.

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-job-output.md

WHAT IT DOES

What get_job_output does on CLIO Adios

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

This tool queries job output logs for inspection purposes. It has no side effects: it does not modify job state, does not execute new code, and does not delete data. The worst-case misuse (reading sensitive logs accidentally) is contained and does not introduce blast radius comparable to write, execute, or destructive actions. Classification as Read is appropriate.

From the tool's definition Tool retrieves 'stdout or stderr output from a Slurm job' — it fetches job logs without modification or execution. The verb 'retrieve' indicates a read-only query operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_job_output Allowed

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

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

FAQ

Questions about get_job_output

What does the get_job_output tool do? +

Retrieve stdout or stderr output from a Slurm job. 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_job_output? +

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

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

Can I rate-limit get_job_output? +

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

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

get_job_output 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_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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