get_job_summary
Get job-level summary from a Darshan log including runtime, process count, and I/O volume.
This record as markdown: /tools/io-github-iowarp-adios-mcp/get-job-summary.md
What get_job_summary does on CLIO Adios
AI agents call get_job_summary 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.
Why get_job_summary is rated Low
This tool retrieves and queries metadata from Darshan logs (a performance monitoring tool for HPC I/O). It returns aggregated job-level information (runtime, process count, I/O volume) without modifying, deleting, or executing external operations. The blast radius is minimal—misuse would only affect visibility into historical performance data, not system state or data integrity.
From the tool's definition Tool name 'get_job_summary' and description 'Get job-level summary from a Darshan log including runtime, process count, and I/O volume' indicate data retrieval with no modification or destructive capability.
Attacks that exploit this kind of access
The rule that runs get_job_summary 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_summary, this is the rule to start with:
get_job_summary is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CLIO Adios, apply this rule, and every get_job_summary call is checked against it from then on.
Questions about get_job_summary
Get job-level summary from a Darshan log including runtime, process count, and I/O volume. It is categorised as a Read tool in the CLIO Adios MCP Server, which means it retrieves data without modifying state.
Register the CLIO Adios MCP server in PolicyLayer and add a rule for get_job_summary: 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.
get_job_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_job_summary 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.
Set action: deny in the PolicyLayer policy for get_job_summary. 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.
get_job_summary 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.
More on CLIO Adios, and thousands of servers like it.
This server
Across the catalogue